Enhanced codepage support for Zowe Desktop

[lnlyssg]

Currently it seems the only part of Zowe desktop that supports any change of codepage is TN3270 which has a limited list of available codepages (there is no sign of the UK ones for example). In addition MVS Explorer and Editor appear to be "stuck" with the default codepage which can cause display issues e.g. #429

Describe your enhancement idea

I would like to see enhanced codepage support, perhaps via a setting in zowe.yaml to specify your desired codepage at a base level, but perhaps the various plugins could be enhanced to allow you to choose a per-user codepage setting?

Describe alternatives you've considered

None

Provide any additional context

N/A

[1000TurquoisePogs]

Hi, the Editor is based upon zowe-common-c which appears to respect tagging on its file api.
The MVS explorer isn't accepting enhancements at this time, but the Editor is so we want to look into this more.
Do you tag your files that are not showing up well for you?
The behavior of untagged files is to assume 1047.
I think our tagging UI does not give a complete list of possibilities but you can tag on USS via "chtag"
It could be helpful across zowe to have a way to change the assumption of untagged files away from 1047, so let's split this codepage concern into two subjects: do we handle tagged files correctly (assuming yes), and do we handle untagged files correctly (seems no)

[lnlyssg]

I'm afraid that tagging doesn't apply because 99% of the time I am editing datasets, not USS files