fix(rerun): honour BROWSERSTACK_RERUN_TESTS so only failed specs re-run [SDK-7124]

[osho-20]

Summary

TRA dashboard Re-run → failed tests only was re-running the whole Cypress suite for EasyJet (browserstack-cypress-cli 1.36.13, GitHub Actions). Root cause is a spec-list format bug in the CLI: obs-api passes the failed specs comma+space separated (BROWSERSTACK_RERUN_TESTS="a.ts, b.ts"), but the re-run code path fed that raw string into the spec glob without stripping the spaces — so the glob never matched the intended specs and the run fell back to the full suite.

What lands here

File	Change
bin/helpers/utils.js	setUserSpecs — route BROWSERSTACK_RERUN_TESTS through fixCommaSeparatedString (the same normalisation every other spec source already gets) before assigning run_settings.specs.
bin/testObservability/helper/helper.js	getReRunSpecs (local cypress run path) — trim each entry of the rerun list before passing to cypress --spec, where a leading space silently drops every spec but the first.
test/unit/bin/helpers/utils.js	Regression test on the rerun branch of setUserSpecs using the ticket's exact 5-spec value.

Why the whole suite ran

sanitizeSpecsPattern wraps a multi-comma spec string in braces for glob. With the raw value it produced:

"{FO-E2E-05.ts, FO-E2E-02.ts, FO-E2E-06.ts, FO-E2E-07.ts, FO-E2E-03.ts}"

Brace alternatives keep the leading space (" FO-E2E-02.ts"), so only the first (space-free) alternative can match. Locally the glob resolves 1/5; on BrowserStack the malformed pattern resolves to nothing and the runner falls back to the full suite — the "every spec re-ran" symptom in the ticket (child build 141199119 ran all 9 specs, incl. 4 never in the payload).

After normalisation the pattern is {FO-E2E-05.ts,FO-E2E-02.ts,...} and resolves to exactly the 5 failed specs.

Test plan

• New regression unit test (setUserSpecs … SDK-7124) — fails on the pre-fix line (asserts the space-mangled string), passes after the fix.
• Full test/unit/bin/helpers/utils.js suite: 391 passing (was 390) — the +1 is this test; the 5 failing (setLocalArgs/setNodeVersion/getVideoConfig) are pre-existing and unrelated (present on a clean master checkout too).
• Standalone reproduction against a 9-spec fixture with the ticket's exact env value, using real glob@7 + the verbatim sanitizeSpecsPattern/fixCommaSeparatedString: pre-fix matches 1/9, post-fix matches exactly the 5 failed specs.

Notes / scope

• Backward compatible: fixCommaSeparatedString is a no-op on already-clean lists; non-rerun runs are unaffected.
• This fixes the CLI-side handling. If the failed-spec env never reaches the runner in a given CI setup (e.g. a GitHub native workflow re-run that replays without env injection), that is a separate Integrations/obs-api delivery concern outside this repo — this change ensures the CLI does the right thing whenever the list is present.

Release

• patch — bug fix only.

Fixes SDK-7124.

[osho-20]

✅ Good to go

File	Status	Reason
bin/helpers/utils.js	✅ All Clear	Covered by all lenses, no issues found
bin/testObservability/helper/helper.js	✅ All Clear	Covered by all lenses, no issues found
test/unit/bin/helpers/utils.js	✅ All Clear	Covered by all lenses, no issues found

↻ This verdict comment is the review anchor — it's updated in place on each run (the gate posts its status separately).

— SDK PR Review Agent