fasWorkflow build command does not train and run if application folder and _commands folder are not siblings under the workflow folderpath

[sanchit056]

Is your feature request related to a problem? Please describe.

1. Training issue - The fastWorkflow build command is not training the command metadata extraction if I keep the directory structure as: my workflow folderpath inside the root directory and then the _commands folder, context_inheritance_model.json, etc. inside that. which in turn is giving the file not found error for routing_definition.json in the fastworkflow installed package (fastworkflow/_workflows/command_metadata_extraction/__comand_info/routing_definiton.json)

2. Run issue - Getting relative import error even if we copy the routing_definition.json file in the required folder:
   ImportError: attempted relative import beyond top-level package
   This is because the sys path folder is our worklow folder which does not contain the application code and is inside another parent folder.