Users/stevenh/ui explorer test

[stevenhorsman]

Relevant issues

Fixes #1536

Depends on zowe/explorer-ui-server#37
zowe/explorer-jes#207

Changes proposed in this PR

• pull in explorer-ui component and add install script for it.

[stevenhorsman]

Converting to draft whilst we decide if we want to continue with the explorer-ui-server separation next release

[NakulManchanda]

From @1000TurquoisePogs

I had a concern about filesystem structure:

• this seems like a shared library rather than a component in itself
• it currently looks that way because it doesnt have its own start.sh script
• today everything in /components does have a start.sh
  so, today scripting can take for granted /components are all the same type of thing, which could be beneficial for some future management tools.
  i was thinking it would be good to move this new not-quite-component code into a new folder such as /lib or /shared

[NakulManchanda]

yes, its not used on its own, rather it get called by three explorers
so, we can have some conventions
shared -> looks better to me - as its still an executable
lib -> can be just for non executable things

[NakulManchanda]

@stevenhorsman @jackjia-ibm
these are ready for review and if all ok, ready to merge
All tests are passing, jack verified the folder structure as well.

old strucutre
component
jes > server app
mvs > server app
uss > server app

Moved structure to new shared folder,
We layout one copy of server instead of three,
We still start three instances of server though.

new structure
component
jes > app
mvs > app
uss > app
shared
explorer-ui-server

As per me,
No documentation required, as for end user, there wont be any difference

Related PR's
zowe/explorer-ui-server#37
zowe/explorer-jes#207
#1545

[jackjia-ibm]

Merge the other PRs first and modify versions in binaryDependencies.