ci: Dynamically assign testbed name for benchmarks

[mhovd]

Ensures that benchmarks are accurately compared

[Copilot]

Pull Request Overview

This PR updates the GitHub Actions workflow files to dynamically assign testbed names for benchmarks using the runner name instead of a hardcoded "orion" value. This change ensures that benchmarks are accurately compared by using the actual runner environment as the testbed identifier.

Key changes:

• Replace hardcoded testbed name with dynamic runner name reference
• Minor formatting improvement to branch specification syntax

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/pr_benchmarks.yml	Updates testbed parameter to use dynamic runner name
.github/workflows/base_benchmarks.yml	Updates testbed parameter to use dynamic runner name and improves branch syntax

[github-actions]

Bencher Report

Branch	ci-benchmark
Testbed	pmcore-runner

⚠️ WARNING: No Threshold found!

Without a Threshold, no Alerts will ever be generated.

• Latency (nanoseconds (ns))

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds flag.

Click to view all benchmark results

Benchmark	Latency	seconds (s)
bimodal_ke_fit	📈 view plot ⚠️ NO THRESHOLD	10.19 s

🐰 View full continuous benchmarking report in Bencher

[mhovd]

We already have this change in pharmsol, and need it in PMcore as well