feat(setup): add optional mode arg to target setup

[fargito]

No description provided.

[greptile-apps]

Greptile Summary

Adds an optional --mode argument (short -m, also read from CODSPEED_RUNNER_MODE) to the codspeed setup command, letting users target a specific executor (or a comma-separated list) rather than always running setup for every executor. The top-level codspeed status command is updated to pass &[] to setup::status, preserving its existing all-executors behaviour.

• get_executors_from_modes is introduced as a central helper that resolves a &[RunnerMode] slice to executor instances, delegating to get_all_executors() when the list is empty.
• setup_executor is extracted into its own async helper, cleaning up the previous inline match block.
• setup::status is updated to accept and honour a modes slice, so codspeed setup status --mode walltime now only shows walltime tool status.

Confidence Score: 4/5

Safe to merge with one fix: the duplicate-executor path in get_executors_from_modes should be guarded before landing.

The refactoring is clean and the new --mode flag behaves correctly for the common cases. The one concrete defect is that passing both the deprecated instrumentation mode and simulation together (or via CODSPEED_RUNNER_MODE) produces two ValgrindExecutor instances, causing duplicate status lines and a redundant second Valgrind setup pass. Once that deduplication is in place, the change is straightforward to merge.

src/cli/setup.rs — specifically get_executors_from_modes

Important Files Changed

Filename	Overview
src/cli/setup.rs	Adds optional --mode / CODSPEED_RUNNER_MODE filtering to setup and setup status; extracts setup_executor helper. Duplicate executor issue when both instrumentation and simulation modes are passed.
src/cli/status.rs	Updates call to setup::status to pass an empty slice (&[]), preserving the existing "show all executors" behaviour for the top-level codspeed status command.

_{Reviews (3): Last reviewed commit: "feat(setup): add optional `mode` arg to ..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 7 untouched benchmarks

---

_{Comparing cod-2831-add-a-codspeed-setup-mode-command (bd8f33e) with main (aca0831)}

[GuillaumeLagrange]

lgtm