Opening files through the filesystemprovider does not listen to encoding specified in profile

[TommyTechh]

Describe the bug

When opening a resource through zowe-ds:/<Profile Name (LPAR)>/ and showing the window in vscode it OFTEN/SOMESTIMES doesn't listen to the encoding property specified in the profile.

If it's opened through the zowe explorer it seemingly always works.

To Reproduce

Steps to reproduce the behavior:

1. Have a profile with encoding 277 and a cobol program with either ÆØÅ in it
2. In vscode create a vscode URI with scheme zowe-ds:/<Profile Name (LPAR)>/
3. You will now see that any # are converted to ¢ and ÆØÅ has been converted $ or something else.

Another way of testing this it to open a file through the zowe explorer, afterwards close vscode and reopen it. It will have the window cached and it will now try and fetch the file again, but with the wrong encoding information

Expected behavior

Should be the same as when it's opened through the zowe explorer and always listen to the profile encoding information

Desktop (please complete the following information):

• OS: Windows 11 23H2
• Zowe Explorer Version: 3.0.3
• (Optional) Zowe CLI Version:
• (Optional) Are you using Secure Credential Store?

Additional context

Perhaps it should be possible to add encoding/codepage information to the query part of the URI.

[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.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.