GH-375 Fixed issue with encodings on USS

[KUGDev]

What It Does

Fixes #375

How to Test

1. Create a USS file with non-latin symbols
2. Call uss.get_content("/path/to/file", file_encoding="UTF-8", receive_encoding="UTF-8"), uss.get_content_streamed("/path/to/file", binary=False, file_encoding="UTF-8", receive_encoding="UTF-8"), uss.download("/path/to/file", "/output/path", binary=False, file_encoding="UTF-8", receive_encoding="UTF-8")
3. Make sure that the content is correct

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

Additional Comments

[codecov]

Codecov Report

❌ Patch coverage is 82.19178% with 26 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.99%. Comparing base (8fe22c2) to head (4289689).

Files with missing lines	Patch %	Lines
.../zos_files/zowe/zos_files_for_zowe_sdk/datasets.py	53.57%	13 Missing ⚠️
src/zos_files/zowe/zos_files_for_zowe_sdk/uss.py	90.78%	7 Missing ⚠️
..._files/zowe/zos_files_for_zowe_sdk/response/uss.py	82.35%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #380      +/-   ##
==========================================
+ Coverage   81.88%   81.99%   +0.10%     
==========================================
  Files          48       48              
  Lines        2771     2893     +122     
==========================================
+ Hits         2269     2372     +103     
- Misses        502      521      +19     

Flag	Coverage Δ
unittests	81.99% <82.19%> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[t1m0thyj]

Apologies for the delayed review, thanks @KUGDev for your contribution! 😁

Have a few questions related to how receive_encoding works in the download method, otherwise LGTM!

[KUGDev]

Hi @t1m0thyj.
Thank you for the review.
Please, read my response on the last comment

[KUGDev]

@t1m0thyj I added functionality to upload and write binary USS files 5ff177ee. For some reason GitHub Action for Python 3.12 does not work properly. I don't think it is necessary to create a separate branch for such changes, but let me know if it would be better to do so.

[t1m0thyj]

Thanks @KUGDev for making updates! Left one more comment.

I think the CI failures were due to a transient Codecov issue, as they passed when re-run.

[t1m0thyj]

When the open method is invoked with wb mode, it will throw an error if encoding argument is provided.

Suggested change

	with open(output_file, "wb" if binary else "w", encoding=receive_encoding) as f:
	with open(output_file, "wb" if binary else "w", encoding=None if binary else receive_encoding) as f:

[KUGDev]

Ah, good catch @t1m0thyj ! Thank you:)
I also noticed that in the data sets part the same functionality is implemented as download + download_binary. I don't know if it is ok to combine them the same way as in the USS part since some SDK users could already utilize that as it is right now. What do you think?
As a workaround I can propose to mark download_binary as deprecated.

[t1m0thyj]

Also good catch on the inconsistency between USS and Data Set APIs 😋

I think combining the 2 methods for data sets into 1 makes sense, as long as we keep the old method deprecated 👍

[KUGDev]

@t1m0thyj sorry, got too deep into changes😅
Let me know if it is ok to stay like that, otherwise I will rollback to the previous version