Disambiguate chromium launcher test check

[ulziibay-kernel]

Summary

• Rename the chromium launcher workflow job from test to chromium-launcher-test.
• This gives branch protection/rulesets a unique required-check context instead of colliding with the server workflow's test job.

Test plan

• Not run; workflow metadata-only change.
• After this merges and runs on main, require the chromium-launcher-test check in the main branch ruleset.

Made with Cursor

---

Note

Low Risk
Workflow metadata-only rename; no application or test logic changes.

Overview
Renames the chromium-launcher GitHub Actions job from test to chromium-launcher-test in .github/workflows/chromium-launcher-test.yaml.

That gives branch protection and rulesets a distinct required-check name instead of sharing the generic test label with the server workflow’s test job. No test steps or commands change—only the job identifier.

^{Reviewed by Cursor Bugbot for commit c6d6e2d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: PR is a workflow metadata-only change that doesn't affect runtime behavior of any kernel service, making deploy monitoring unnecessary.

To monitor this PR anyway, reply with @firetiger monitor this.