Fix logger config

[pem70]

What It Does
Fixes the bug the logger config would affect other Python application logger [#314].

How to Test

Review Checklist
I certify that I have:

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

Additional Comments

[traeok]

Changes look good to me, thanks Peizhao!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.85%. Comparing base (41cb81e) to head (1011d58).
Report is 142 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #313      +/-   ##
==========================================
- Coverage   90.03%   89.85%   -0.19%     
==========================================
  Files          53       53              
  Lines        2751     2808      +57     
==========================================
+ Hits         2477     2523      +46     
- Misses        274      285      +11     

Flag	Coverage Δ
unittests	89.85% <100.00%> (-0.19%)	⬇️

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.

[zFernand0]

This does resolve the problem of logging statements going to the python_sdk.log file 😋

---

I like the Log.close_[file/console]_output()functions. 🙏🏽

Is it expected that any logging.[debug,info,error]("test") will turn on console_output?(i.e. it's equivalent to running Log.open_console_output())

In contrast, the closeAll() function keeps the logger disabled even after a logging.[xyz]() call occurs.

Expand this section to vew a small test script

profile = ProfileManager().load(profile_type="zosmf", validate_schema=False)
ds = Datasets(profile)
console = Console(profile)
jobs = Jobs(profile)

Log.setAllLoggerLevel(logging.DEBUG)
# Log.closeAll() # Keeps console_output off
Log.close_console_output() # Gets enabled after a `logging.` call
# Log.close_file_output()

res = console.issue_command("D T") # You won't see a debug log in the console
print(res['cmd-response'])

logging.error("---- Test ----") # This turns on the consloe_output

res = ds.list('sys1.parmlib*') # You should not see a debug log in the console
for v in res["items"]:
    print(v["dsname"])

[pem70]

This does resolve the problem of logging statements going to the python_sdk.log file 😋

I like the Log.close_[file/console]_output()functions. 🙏🏽

Is it expected that any logging.[debug,info,error]("test") will turn on console_output?(i.e. it's equivalent to running Log.open_console_output())

In contrast, the closeAll() function keeps the logger disabled even after a logging.[xyz]() call occurs.

Expand this section to vew a small test script

It is not an expected behavior, and should be fixed with the update.

[zFernand0]

Thank you for addressing the comment 😋

[github-actions]

Release succeeded for the main branch. 🎉

The following packages have been published:

• pypi: zowe-python-sdk-bundle-1.0.0.dev18
• pypi: zowe_core_for_zowe_sdk-1.0.0.dev18
• pypi: zowe_zos_console_for_zowe_sdk-1.0.0.dev18
• pypi: zowe_zos_files_for_zowe_sdk-1.0.0.dev18
• pypi: zowe_zos_jobs_for_zowe_sdk-1.0.0.dev18
• pypi: zowe_zos_tso_for_zowe_sdk-1.0.0.dev18
• pypi: zowe_zosmf_for_zowe_sdk-1.0.0.dev18

_{Powered by Octorelease 🚀}