Run appsody init from the host OS to avoid docker binding issues

[sghung]

Right now, the appsody init is run in container. We need to run appsody init outside of the container to avoid docker bind issues. During appsody init, we have to map the m2 directory such that the init updates the OS so that the IDE can compile properly. However, that causes issues on Windows when using enterprise accounts and doesn't work for some future project types appsody plans to support (they did that m2 hack via binding just for us).

This is a parent issue for us to track all the work required from other teams before the Appsody tools team can verify everything has come together properly.

[sghung]

Currently blocked by:

• Run appsody init when creating a project from an Appsody template Increase code coverage of functional tests #95
• Ability for Codewind CLI to run extra commands when creating project Ability for Codewind CLI to run extra commands when creating project #270
• Ensure Appsody CLI is available if user wants to use Appsody in Codewind Ensure Appsody CLI is available if user wants to use Appsody in Codewind #271
• Call the codewind CLI for project creation in the IDEs Call the codewind CLI for project creation in the IDEs #371

[sghung]

We are still working towards DCUT for this item. We are currently not blocked by anything, our team is making changes to the vscode and eclipse codewind extensions. In addition, we're making changes to the codewind-installer.

[sghung]

Closing, work was done for 0.4.0