Allow users to open data sets and USS files in another codepage

[t1m0thyj]

Proposed changes

⚠️ This PR depends on #2634 - merge that one first, then update base branch of this PR

• Resolves Add ability to download/view/upload Datasets/Members/USS files in non-standard codepage #2435
• Fixes Editing a USS file that has an existing encoding overwrites it with a binary tag rather than keep the existing encoding #2576
• Also backported ZoweLocalStorage class from "next" branch to store recent codepage history

How to Test

• Test opening data set & USS file in default EBCDIC encoding
• Test opening data set & USS file in binary mode
• Test opening data set & USS file in custom encoding
  • In same session, close and re-open them - custom encoding should be remembered
  • Test with encoding in z/OSMF profile - custom encoding should take precedence
• Test saving USS file tagged as ISO8859-1 - USS tag should not change

Release Notes

Milestone: 2.14.0

Changelog:

• Added "Open with Encoding" feature to open data sets and USS files in a non-standard codepage.
• Fixed issue where USS file tag could get overwritten when changes to file are uploaded.

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

ze-encoding.mp4

[adam-wolfe]

Think this also resolves #887.

[traeok]

Thanks @t1m0thyj for this work on enhancing encoding support 😋
Just left a couple comments on the localized strings and the openPS function:

[codecov]

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (a8e1155) 93.15% compared to head (f1130e7) 93.24%.

Files	Patch %	Lines
packages/zowe-explorer/src/shared/actions.ts	0.00%	3 Missing ⚠️
packages/zowe-explorer/src/shared/utils.ts	95.00%	3 Missing ⚠️
packages/zowe-explorer/src/uss/actions.ts	50.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2594      +/-   ##
==========================================
+ Coverage   93.15%   93.24%   +0.09%     
==========================================
  Files         101      102       +1     
  Lines       10323    10471     +148     
  Branches     2183     2237      +54     
==========================================
+ Hits         9616     9764     +148     
  Misses        706      706              
  Partials        1        1              

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

[t1m0thyj]

Moved most of the refactoring into a separate PR (#2634) to hopefully make the encoding changes easier to review

[awharn]

This looks good to me! Tested with a dataset using a double byte encoding, and it works great! Only comment is that creating a profile or team config is starting to get a bit long via the UI, with a bunch of questions around encoding, certificates, APIML base path, port, protocol, scheme, timeouts, etc. Nothing against this PR, just an observation.

[traeok]

This implementation looks and works great! Thanks @t1m0thyj for this feature, I like the UX as well 😁

One thing that might be worth looking into is offering the "Open with Encoding" command in the Command Palette - it might involve some adjustments to the command itself, but would be a nice shortcut so users can quickly change the encoding of the active editor 😅

[JillieBeanSim]

works great! thanks @t1m0thyj

The base branch was changed.

[sonarcloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

5 New issues
0 Security Hotspots
No data about Coverage
0.6% Duplication on New Code

See analysis details on SonarCloud