ci: lift Bazel test timeouts on release runs

[tinder-maxwellelliott]

Summary

• The Release workflow's reusable release_ruleset step runs bazel test //... on a single cold runner. On v44.0.0 that killed //tests:e2e_test at the enormous 3600s cap (TIMEOUT in 3600.0s) and skipped attest/publish/binaries.
• Add a .bazelrc test:no-test-timeouts config (--test_timeout=21600, GitHub's 6h job ceiling) and pass it via bazel_test_command in release.yaml.
• PR CI is unchanged, so per-size timeouts still catch hangs where each suite has its own runner.

Test plan

• bazel test //tools:benchmark_test --config=no-test-timeouts --announce_rc reports test:no-test-timeouts ... --test_timeout=21600 and the test passes
• After merge, re-cut (or move) the v44.0.0 tag so the Release workflow checks out a commit that includes this fix, then confirm release / build gets past Test

Made with Cursor