Accommodating keystore parameters with spaces

[1000TurquoisePogs]

Description

Recently we've seen users that have spaces in their keystore such that $KEY_ALIAS could be misinterpreted.
A solution is to put quotes around the parameters, and that's what was done successfully in the web explorers such as here https://github.com/zowe/explorer-jes/blob/master/bin/start.sh#L47-L52
I tried to find all occurrences of variables that might need spaces, though perhaps having quotes everywhere is not a bad idea.

Type of change

Please delete options that are not relevant.

• (fix) Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

I'll run the automated tests on this to see how it does.

[1000TurquoisePogs]

It looks like some of the CI actions are pointing at origin rather than my fork. Should I create this PR on origin instead if possible?

[jandadav]

Hello, the only problematic workflow should be the Sonarqube. Otherwise the actions should run even against forks. But if it's not working, try it from the origin. Let us know if you're facing problems there.