Environments

[andreasphil]

This PR makes several changes to our frontend build setup:

• Moved Vitest related config to its own file to keep the Vite configuration more compact
• Run E2E tests against the production application rather than the dev server
• Add a function to infer the environment during runtime so it doesn't need to be statically defined during build*
• Conditionally initialize Sentry reporting only for permanent environments (production, staging, UAT)
• Replace the hardcoded staging environment in the Sentry config with the inferred environment
• Use the Sentry Vite plugin only for production builds and only if it is properly configured
• Along with some minor cleanup.

✅ Todo: Double check the Sentry setup for the backend too. That's probably already fine though (59a4d2b)

(*) This is currently just a bunch of heuristics and not super pretty, but I encapsulated it in a function so we can easily replace that once we have a better solution.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
97.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud