tests: Behavior-driven integration and e2e tests using WebdriverIO

[traeok]

Proposed changes

This pull request implements the following items:

• [x] Behavior-driven integration test bed using WebdriverIO framework and CucumberJS
• [x] Test-driven integration test bed using vscode-test and Mocha
  • Old tests were removed from this test bed, but its still in place to offer flexibility and enable stubbing where needed
• [x] End-to-end (e2e) test bed using WebdriverIO and CucumberJS
  • Screenshots for end-to-end failing test steps (thanks @t1m0thyj 🎉)
• [x] Documentation for how to set up and run tests (both e2e and integration)
• [x] Launch configurations for running e2e and integration tests
• [x] Initial foundation/list of e2e and integration tests as listed in #2322

How to test

• Checkout the tests/wdio-impl branch in the ZE repo
• Run pnpm install && pnpm build at the root of the repo
• Refer to the steps in packages/zowe-explorer/__tests__/__e2e__/README.md to prepare your environment for end-to-end testing
  • Once the environment is prepared, run cd packages/zowe-explorer && pnpm tests:e2e to run tests
• Refer to the steps in packages/zowe-explorer/__tests__/__integration__/README.md to ensure your environment is ready for integration tests
  • Once the environment is prepared, run cd packages/zowe-explorer && pnpm tests:integration to run tests

Both test scripts should succeed provided that:

• the user's Zowe config has at least 3 profiles that can be accessed during the integration tests
• the environment variables defined in the __e2e__/.env file refer to valid filters and items on the test system during the e2e tests

In addition, notice the new step in the build stage on Ubuntu/Node 20 titled "Integration tests" - these should be passing with the latest changes on this branch.

Release Notes

Milestone: v3

Changelog:

• Added behavior-driven integration tests and end-to-end tests to verify extension behavior and catch issues during Zowe Explorer development. #2322

Types of changes

What types of changes does your code introduce to Zowe Explorer? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Updates to Documentation or Tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

• [x] I have read the CONTRIBUTOR GUIDANCE wiki
• [x] PR title follows Conventional Commits Guidelines
• [x] PR Description is included
• [ ] gif or screenshot is included if visual changes are made
• [x] yarn workspace vscode-extension-for-zowe vscode:prepublish has been executed
• [x] All checks have passed (DCO, Jenkins and Code Coverage)
• [ ] I have added unit test and it is passing
• [x] I have added integration test and it is passing
• [x] There is coverage for the code that I have added
• [x] I have tested it manually and there are no regressions found
• [x] I have added necessary documentation (if appropriate)

Further comments

I noticed that we still had a few lint errors in the existing unit tests. I've corrected those as part of this branch.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.62%. Comparing base (80d6e37) to head (cfac68b).

:exclamation: Current head cfac68b differs from pull request most recent head 3af4923

Please upload reports for the commit 3af4923 to get more accurate results.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## next #2927 +/- ## ========================================== - Coverage 92.63% 92.62% -0.01% ========================================== Files 109 109 Lines 11008 11008 Branches 2347 2343 -4 ========================================== - Hits 10197 10196 -1 - Misses 809 810 +1 Partials 2 2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[sonarcloud[bot]]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
2.5% Duplication on New Code

See analysis details on SonarCloud

[traeok]

I do notice warnings about a broken lockfile when first running pnpm install with this branch. I believe last time we saw this was when pnpm 9 was used instead of 8 by the developer of the branch. I have 8.15.8. Still testing functionality but wanted to mention this. I see a lot of scripts/workflows using 9 but also see engines: {pnpm: '>=8'} in lockfile and deployment pulls 8 when doing search for pnpm in repo. We can go to 9 but need to let all devs know to update

Sorry about that @JillieBeanSim, I was doing some tests with pnpm 9 and forgot to switch back to pnpm 8 - it ended up updating the lockfile to v9 as a result. I've addressed this in commit 3af4923 👍