adding test-specific tsconfig files in appropriate dirs

[ATorrise]

What It Does
Configures typescript test files to include jest type information, reducing the amount of distracting, not-real-yet-still-highlighted-as-such errors when working in test files

How to Test
Pull branch and start opening up some test files, making sure there are no errors like:

Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.ts(2582) 

Review Checklist
I certify that I have:

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6f30932) 91.03% compared to head (17a076d) 91.03%.
Report is 2 commits behind head on next.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #1996   +/-   ##
=======================================
  Coverage   91.03%   91.03%           
=======================================
  Files         635      635           
  Lines       18610    18610           
  Branches     3859     3859           
=======================================
  Hits        16941    16941           
  Misses       1668     1668           
  Partials        1        1           

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

[zFernand0]

TL;DR: LGTM! 😋

---

I like this solution a lot.
It resolved the problem of having to import @types/jest in a random file for those Jest functions (describe, afterAll, ...) to be recognized as actual functions.

I'm curious if we could do some technique to reduce duplication. Something like...

"extends": "../../tsconfig.json",

One thing to keep in mind that this only fixes tests that are under the packages/PKG/__tests__/ directory. For example, this won't help with
packages/imperative/src/utilities/__tests__/CliUtils.unit.test.ts since the tsconfig.json is under packages/imperative/__tests__/ 😋

[zFernand0]

One thing to keep in mind that this only fixes tests that are under the packages/PKG/tests/ directory. For example, this won't help with
packages/imperative/src/utilities/tests/CliUtils.unit.test.ts since the tsconfig.json is under packages/imperative/tests/ 😋

I take that back.
Even files from within the imperative/src/utilities/__tests__/ work now 😋

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[traeok]

LGTM, thanks @ATorrise!

[github-actions]

Release succeeded for the next branch. 🎉

The following packages have been published:

• npm: @zowe/secrets-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/imperative@8.0.0-next.202401041721
• npm: @zowe/cli-test-utils@8.0.0-next.202401041721
• npm: @zowe/core-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-uss-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/provisioning-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-console-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-files-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-logs-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zosmf-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-workflows-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-jobs-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/zos-tso-for-zowe-sdk@8.0.0-next.202401041721
• npm: @zowe/cli@8.0.0-next.202401041721

_{Powered by Octorelease 🚀}