chore: test accepance against QA and Prod

[eliobischof]

Enables manually triggering acceptance tests against a Zitadel backend on Qa EU1 and Prod US1.
Triggers both every morning at 6 AM.
Needs the GitHub secrets ENV_FILE_CONTENT_ACCEPTANCE_QA and ENV_FILE_CONTENT_ACCEPTANCE_PROD

⚠️ Some of these tests time out #304

Contributes to #51

Definition of Ready

• I am happy with the code
• Short description of the feature/issue is added in the pr description
• PR is linked to the corresponding user story
• Acceptance criteria are met
• All open todos and follow ups are defined in a new ticket and justified
• Deviations from the acceptance criteria and design are agreed with the PO and documented.
• Vitest unit tests ensure that components produce expected outputs on different inputs.
• Cypress integration tests ensure that login app pages work as expected. The ZITADEL API is mocked.
• No debug or dead code
• My code has no repetitions

[vercel]

@eliobischof is attempting to deploy a commit to the zitadel Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
typescript-login	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2024 11:55am