automation: Backport e2e tests to 2.8

[yonasberhe23]

Summary

Fixes # https://github.com/rancher/qa-tasks/issues/1189

Technical notes summary

Backport the provisioning e2e tests (and their dependencies) to 2.8

• Actions on cluster: https://github.com/rancher/dashboard/pull/9946
• Support page: https://github.com/rancher/dashboard/pull/9715
• Cluster management: https://github.com/rancher/dashboard/pull/10161
• Aws prov: https://github.com/rancher/dashboard/pull/10384 -- Note: needed to add rke2PageTitle() fn manually to make aws test pass (the fn came from this https://github.com/rancher/dashboard/pull/10284)
• Address Jenkins failures: https://github.com/rancher/dashboard/pull/10442
• Azure prov: https://github.com/rancher/dashboard/pull/10508
• Added some fixes to make tests pass -- https://github.com/rancher/dashboard/pull/10551/commits/cca20dc6f989bcc7e02b685d8499bed7b44f8ad8 -- https://github.com/rancher/dashboard/pull/10551/commits/e001ca13ec517ef8cd1718c51fbc28887b8f7925 -- https://github.com/rancher/dashboard/pull/10552/commits/41fdf416f71df3b0806e3727645ac172c1dd2186 -- https://github.com/rancher/dashboard/pull/10552/commits/3f1d1a1f66882291d20e48ea73ba34109b4cccf9

Update: I've also added the changes to support running e2e tests in parallel in this backport to reduce the time it takes for the test run to complete https://github.com/rancher/dashboard/pull/9887

Checklist

• [ ] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• [x] The PR has a Milestone
• [x] The PR template has been filled out
• [x] The PR has been self reviewed
• [x] The PR has a reviewer assigned
• [ ] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• [ ] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[izaac]

Thanks for consolidating all this @yonasberhe23, as discussed offline these are existing tests recently merged on latest but I'll defer to @richard-cox the code implementation to make it work on the 2.8 branch.

This is the first backport too so this will set precedence for future backports and having feedback from dev is very important. LGTM from me.