Migrate pr1840

[zFernand0]

What It Does

This is the first PR of many more to come in before the Zowe V3 GA date.
The intention is to migrate the changes done in the following PR:

• Restore Jest sonar reporter and bump workflow timeout #1840

How to Test

• Verify that the pipeline can go for longer than 75 minutes
• Verify that the Sonar reporter is successfully reporting based on test results

In other words, let's give the pipeline some time to complete. 😋

Review Checklist
I certify that I have:

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

Additional Comments

I wanted to have this as an example of a clean migration from master to next.
The will be PRs where conflicts between the two branches will arise, so be cautious during any and all migration PRs 😋

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 357 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[zFernand0]

Should this PR have the release-major label, so that we can have a 8.0.0-next.timestamp in our GH releases and eventually in public NPM ?

[t1m0thyj]

Should this PR have the release-major label, so that we can have a 8.0.0-next.timestamp in our GH releases and eventually in public NPM ?

I'm not opposed to merging this PR with release-major as long as we're aware of the implications. This would mean that Imperative has a 6.0.0-next.timestamp release published until we successfully complete the migration of Imperative into the Core SDK.

[zFernand0]

Should this PR have the release-major label, so that we can have a 8.0.0-next.timestamp in our GH releases and eventually in public NPM ?

I'm not opposed to merging this PR with release-major as long as we're aware of the implications. This would mean that Imperative has a 6.0.0-next.timestamp release published until we successfully complete the migration of Imperative into the Core SDK.

Since the versionIndependent was removed in the vNext branch already, we should end up with an Imperative 8.0.0-next.timestamp 😋
However, I believe that this is what we want since it's not set in stone that the Imperative package will be merged into core. 😋