Minimize the size of API ML

[anton-brezina]

Is your feature request related to a problem? Please describe.
A follow up on spike 899.

Describe the solution you'd like
Use the new jars to deploy on mainframe.
After this change we do not intend to use the fat jars anymore so we intend to stop publishing them.
(stretch) Verify whether there has been a change in the lib file and upload only the changed jars.
Change the zowe install packaging to reflect the new API ML deployment.

Describe alternatives you've considered
Keep the fat jars thus growing the size of the API ML (maybe a caching service modification).

Additional context
899.
To consider - 200MB are about the topline of the API ML size which we should not cross. The whole Zowe should fit within 512MB.

Tasks

• Understand why the XML instead of JSON is returned by default from Discovery service.
• Understand why the lite-lib-jar isn't properly created when the tasks are run together - @balhar-jakub
• Remove version number from the name of the JARs - @balhar-jakub
• Confirm new lib jar and new service jars are published to artifactory, if not change build so they are. - @taban03
• Changing the build of zowe-install-packaging to pull down new lib jar - @taban03
• Change zowe-install-packaging so new lib jar is installed in correct place(s) @jordanCain
• Change apiml start script(s) to use new lib jar @jordanCain
• Update APIML package.json so launch configurations are using new JARs - @balhar-jakub

[jandadav]

Steven Horsman suggests to follow the explorer case https://github.com/zowe/explorer-ui-server/blob/master/manifest.yaml