test(benchmarks): trace every benchmark through a shared config

[glennawatson]

What kind of change does this PR introduce?

Benchmarks and CI.

What is the new behavior?

Every benchmark is traced through a shared config, and the benchmark workflow runs them all.

• Adds Interaction and contended WhenChanged benchmarks.

What is the current behavior?

Each benchmark declares its own jobs and diagnosers, and the workflow runs one chosen suite.

What might this PR break?

None.

Checklist

• I have read the Contribute guide
• Tests have been added or updated (for bug fixes / features)
• Docs have been added or updated (for bug fixes / features)
• Changes target the main branch
• PR title follows Conventional Commits

Additional information

[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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.73%. Comparing base (f1e7aa2) to head (0f77b42).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #101   +/-   ##
=======================================
  Coverage   99.73%   99.73%           
=======================================
  Files         288      288           
  Lines       11537    11537           
  Branches     1256     1256           
=======================================
  Hits        11506    11506           
  Misses         18       18           
  Partials       13       13           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.