Doc string enforcer and annotations

[pem70]

What It Does
Update current doc strings, introduce doc string check, and update annotation for all methods.
[#279] [#309] [#280]

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

[codecov]

Codecov Report

Attention: Patch coverage is 99.16667% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.91%. Comparing base (2dbb721) to head (711ecd8).
Report is 97 commits behind head on main.

Files with missing lines	Patch %	Lines
.../zos_files/zowe/zos_files_for_zowe_sdk/datasets.py	95.83%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #312      +/-   ##
==========================================
- Coverage   90.11%   89.91%   -0.21%     
==========================================
  Files          53       53              
  Lines        2773     2816      +43     
==========================================
+ Hits         2499     2532      +33     
- Misses        274      284      +10     

Flag	Coverage Δ
unittests	89.91% <99.16%> (-0.21%)	⬇️

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.

[traeok]

LGTM, thanks @pem70

[t1m0thyj]

Looks pretty good, thanks @pem70!

Left minor comments that are unresolved from #307

[zFernand0]

Hey @pem70,

When resolving these merge conflicts, remember to remove the basicConfig setup (removed in #313)

To avoid unintentional regressions in the future you can do either of the flowing:

• Create new branches based off of the main branch.
• If branches are created from branches other than main, select the corresponding base branch when creating PRs (and not the main branch). That way you don't have to worry about making the same changes in different branches.
  For example:
  • branch_A_based_on_main > branch_B_based_on_branch_A > branch_C_based_on_branch_B,
    
    • PR#1: base: "main" <- compare: "branch_A_based_on_main"
    • PR#2: base: "branch_A_based_on_main" <- compare: "branch_B_based_on_branch_A"
    • PR#3: base: "branch_B_based_on_branch_A" <- compare: "branch_C_based_on_branch_B"

Doing the above should:

1. Avoid possible regressions
2. Allow PRs to be merged in any order
3. Decrease the number of files changes on each PR
4. Make PR reviews go faster

[t1m0thyj]

LGTM, thanks @pem70!