Allow users to contribute translations with POEditor

[t1m0thyj]

Proposed changes

Created a POEditor project where users can contribute translations. Added two dev scripts:

• scripts/generatePoeditorJson.js - Generates l10n json file in a format that can be imported into POEditor
• scripts/downloadPoeditorL10n.js - Downloads user-contributed translations in a format that can be bundled in VSIX

To maintain these translations going forward:

• Every time we enter code freeze we should follow step 5 added to the wiki article Preparing for release to upload any new l10n terms that have been added.
• To include user-contributed translations there is nothing we need to do 🙂 The deployment workflow will automatically download and bundle them in future v3 releases.

This PR also cleans up some redundant localization strings and fixes an issue where the string "Favorites" was not always being localized which could cause ZE activation to fail.

TODO:

• Test adding contributors to POEditor project
• Test translation with format strings like {0} and {1}
• Update wiki to mention POEditor upload at code freeze
• Update readme to encourage contributing translations

Release Notes

Milestone: v3

Changelog: N/A

Types of changes

What types of changes does your code introduce to Zowe Explorer?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Updates to Documentation or Tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

• I have read the CONTRIBUTOR GUIDANCE wiki
• PR title follows Conventional Commits Guidelines
• PR Description is included
• gif or screenshot is included if visual changes are made
• yarn workspace vscode-extension-for-zowe vscode:prepublish has been executed
• All checks have passed (DCO, Jenkins and Code Coverage)
• I have added unit test and it is passing
• I have added integration test and it is passing
• There is coverage for the code that I have added
• I have tested it manually and there are no regressions found
• I have added necessary documentation (if appropriate)
• Any PR dependencies have been merged and published (if appropriate)

Further comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.40%. Comparing base (50f57ee) to head (28757bf).

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #2894   +/-   ##
=======================================
  Coverage   93.40%   93.40%           
=======================================
  Files         121      121           
  Lines       10834    10835    +1     
  Branches     2280     2232   -48     
=======================================
+ Hits        10119    10120    +1     
  Misses        713      713           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zFernand0]

😻Love this enhancement😻

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[anaxceron]

Nicely done -- thank you @t1m0thyj

[traeok]

Thanks for your work on this @t1m0thyj, this will make it a lot easier to contribute ZE translations moving forward 😋
LGTM - tested on Windows and the script works as expected

[zFernand0]

Changes LGTM! 😋
I do have one small change that might need to be addressed😋