Zowe Explorer v2 & v3: Should always prioritize encoding specified in profile

[TommyTechh]

This most likely also relevant for: #3410

Describe the bug

In Zowe Explorer v2 and v3, when opening a job it will not use the encoding specified in the profile. In V3 an option to "Open with encoding" was added where you can select the encoding from the profile. But why? We specified the encoding option to always ensure that the files opened will use our encoding. This seems to be a problem in more code page related issues.

To Reproduce

Steps to reproduce the behavior:
Open a job output with ÆØÅ characters and see that the code page is wrong. Now "Open with encoding" and use the profile encoding and see that the code page is correct.

Expected behavior

The encoding specified in the profile should always be the first priority even if the file meta data says otherwise.

Desktop (please complete the following information):

OS: Windows 11 23H2
Zowe Explorer Version: 2.18.0 & 3.1.1
(Optional) Zowe CLI Version:
(Optional) Are you using Secure Credential Store?
Additional context

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[TommyTechh]

Hi @t1m0thyj,

I see this is closed, which is exciting. Is this planned to be released with Zowe Explorer 3.1.2? And if not, can it be prioritized.

Thanks in advance!