Migrate automated browser testing from Jetstream1 to Jetstream2

Problem/Opportunity Statement

Jetstream1 will be shut off on July 1. Exosphere's CI pipeline currently uses Jetstream1 for headless browser testing. We need to switch to using Jetstream2 for this.

What would success / a fix look like?

• Store Jetstream2 credentials for TG-INI210003 in CI/CD variables
• Use Jetstream2 for automated browser testing
• Update instructions to new contributors who need to set up browser testing in the CI pipeline on their fork repos