Now that we have benchmark regression testing in place for unit tests, we should change our performance benchmark and stress test e2e tests to run in a separate CI job on macOS latest, Windows latest, and Ubuntu 24 Arm.

This CI job should fail if performance drops by more than 40%. The CI job should be similar to the benchmark job but should be called e2e-benchmark. It should be part of ci.yml, not a separate workflow Current performance and stress tests from the e2e project should run in the e2e-benchmark job but no longer be run in the benchmark job.

The e2e benchmarks should be in the workspace-e2e project. The Jest and TypeScript configurations, nx.json as well as project target should follow the workspace project setup for benchmarks.

The benchmarks should use the same Jest-like describe-it structure as the workspace benchmarks.

If e2e benchmarks use create-nx-workspace, they should use the same version as the nx version currently installed.

Format the code. Verify commands used in CI jobs manually in your local environment, don't ask the user to run them or skip them.