E2E Test Selection:
The changes are purely GitHub Actions workflow configuration changes:

1. run-performance-e2e-release.yml: Added permissions block (contents: read, id-token: write, actions: write) to enable the reusable workflow to use id-token and actions properly.

2. run-performance-e2e.yml: Modified the concurrency group to include build_variant parameter, preventing experimental (exp) and release/direct (rc) builds from sharing the same queue and canceling each other.

These are CI infrastructure improvements that:

• Do not modify any application code
• Do not modify any test code or test infrastructure
• Do not affect how tests execute or what they test
• Are purely about workflow permissions and concurrency management

No E2E tests are needed because there's no application behavior change to validate. The workflow changes would be validated by the CI system itself running successfully, not by E2E tests.

Performance Test Selection:
While these changes are to performance test workflow files, they don't modify the actual performance test code or any application code that would affect performance. The changes are about GitHub Actions permissions and concurrency group naming - purely CI infrastructure concerns. Running performance tests wouldn't validate these workflow configuration changes; the workflow changes are validated by the CI system running successfully. No performance impact to the application.