Note: this likely needs to be done by a project admin for Mongosh. Should verify with a simple evergreen task that tries to connect to an SPI using the saved variables

Variables to add to the project:

• streams_e2e_spi_connection_string: The connection string for the test SPI in cloud-dev
• streams_e2e_db_user: The username for an admin DB user in the "Atlas Streams Test Crew / "MongoDB Shell Integration Testing" cloud-dev org/project
• streams_e2e_db_password: The password for the above DB user
• streams_e2e_cluster_connection_string: The connection string for the cluster test-cluster-gcp in the above project, including the auth credentials

I (Marcus) can send the values over via PrivateBin. These should be added as private variables (docs) since they contain secrets. Then, we can reference them in the .evergreen.yml file for mongosh similarly to how we currently access AWS secrets for the AWS E2E tests, like:

env:
  STREAMS_E2E_SPI_CONNECTION_STRING={streams_e2e_spi_connection_string}
  STREAMS_E2E_DB_USER={streams_e2e_db_user}
  STREAMS_E2E_DB_PASSWORD={streams_e2e_db_password}
  STREAMS_E2E_CLUSTER_CONNECTION_STRING={streams_e2e_cluster_connection_string}