Move the APIML components into the new components folder and remove sed injection of properties

[stevenhorsman]

As a Zowe user,
I want to be able to start the api-mediation services with the configuration passed in at runtime and have a separate user_directory/workspace for my instance data
so that I can make changes to my zowe config without having to reinstall and lose my config.

Details/notes

• We'll follow the pattern set out in Launch Zowe with PARMLIB controlled configuration data running in a workspace directory #433 for launching a component and apply it to the APIML services

• During configure we'll need to inject new properties into run-zowe.sh
  DISCOVERY_PORT
  CATALOG_PORT
  GATEWAY_PORT
  VERIFY_CERTIFICATES - boolean saying if we accept only verified certificates

• Modify the current api-layer services to go into a new directory - either api-mediation, or the 3 separate services depending on the outcome of the question - there needs to be a minimum of a start.sh script in <zowe_root_dir>/components//bin which uses the shell variables to start the service(s) without injection.

• Add the new api-ml services/component to the LAUNCH_COMPONENTS list and remove the old code

• Remove temp workaround of static def injection

• Tidy up run script to only create mediation artefacts if it is in the launch components

• Document changes - Update api-mediation paths docs-site#726 and Componentised scripts api-layer#398 awaiting review

• Create validation script for api-ml #755 covers the follow up story about doing component validation for APIML similar to Component variable validation for Files API service #445

Questions?

• Are the 3 api components co-requisites - is there are valid scenario where a customer might just run 1/2 of these services or should we treat the 3 services as a single component? Single component

Acceptance Criteria

Given an run-zowe.sh forked script with defining all the require properties (listed above)
When I run start ZOWE to drive the script
Then ZOWE should start successfully
And when I look at the zowe job address spaces through display active, I can see the api mediation services active
And The api services should be available on ports <DISCOVERY_PORT>, <CATALOG_PORT> and <GATEWAY_PORT>

//TODO - once the question of how many components is solved it would be good to test each component in isolation for future reasons