Improved Pester Test Integration

This is partially due to a Discord channel chat but also some nice to haves I've been thinking about.

Running tests manually is fine but it seems like we could make this much more useful. Some use cases I am imagining.

• Changes are made in dev, promoted to prod, tests run in prod after deployment
• An increase in app token login failures, run tests to verify access
• Changes are made throughout the day, run nightly tests

While I do think a lot of this is possible outside PSU, I do think that surfacing this in the platform would be very helpful. We don't need it to be extremely complicated but offering a few more integration points would be nice.

• More configurable test execution options (suite, cases, etc) to limit which tests are run
• Triggers can run test suites\cases (git sync in prod, run tests)
• Triggers based on test results (failed tests, run email script)
• Scheduled test runs (nightly tests)
• Improved test run reporting (similar to job runs with more filtering, origin, rerun etc)
• General documentation around running Playwright in PSU (service desktop and accounts etc)