End-to-end Jobs API service component with config driven through PARMLIB

[stevenhorsman]

As a Zowe user,
I want to be able to start the jobs apis service with the configuration passed in at runtime via a PARMLIB 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
This is the jobs version of #435. Most of the infrastructure work will be done in that issue.

Install

• Update jobs/jobs-zowe-server-package/src/main/resources/scripts/jobs-api-server-start.sh have environment variables from PARMLIB rather than sed blocks
• Add a new parameter to PARMLIB: JES_API_PORT
• Remove the zowe-explorer-api-configure.sh file entirely.
• Split out issue to validate the properties to check if JES_API_PORT - to see if the port is available, need to work out how if any to handle duplicated properties

Do we need to create a migrator between PARMLIBs at this point, or let the user do that themselves?

• Based on the outcome of End-to-end Files API service component with config driven through PARMLIB #435, we need to generate a static api-def at configure, and use Vitek's trick to label the address space. JES API code is initially EAJ1

Acceptance Criteria

Given a PARMLIB entry including JES_API_PORT set to <JES_API_PORT>
When I start Zowe using that parmlib
Then Zowe should start without any problems
And the jes APIs should have a api definition pointing at port <JES_API_PORT>
And when I look at the zowe job address spaces through display active, I can see the unique JES API code added