Pin Localizations for Zowe Explorer releases

[MarkAckert]

Opening this as an issue to gather feedback.

Currently Zowe Explorer builds download localizations from a directory in Artifactory, sorting by the lastModifiedTime to pick up the latest build.

This is useful for nightly and on-demand developer builds, but for release builds, it would be ideal to pin to a specific localization archive so builds are fully reproducible and deterministic.

This would require a few changes to the release process:

• Promoting localizations from libs-snapshot-local to libs-release-local during release
• Tracking the pinned version of localizations (within the repo, ideally)
• Improvements to downloadLocalizations.js pulling the pinned version of localization artifacts during releases, and retaining the existing behavior otherwise.

Question:

• Are there are other artifacts pulled down dynamically which could or should be pinned?

[zFernand0]

Personally, I think these suggested changes would be great for deterministic release builds.

Also, I know @phaumer has helped a ton in the past with l10n automation.
Curious to get their thoughts on the matter.

I'm not aware of other artifacts being pulled down dynamically.