useRunnerGroupsVisibility = true - ARC scaling wrong runners

Checks

• I've already read https://github.com/actions-runner-controller/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.

Controller Version

v0.25.2

Helm Chart Version

0.20.2

CertManager Version

1.8

Deployment Method

Helm

cert-manager installation

correct

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
• I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
• My actions-runner-controller version (v0.x.y) does support the feature
• I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue

Resource Definitions

-

To Reproduce

1. Create "general-dev" + "test-dev" Runner Groups in Github
2. Deploy ARC with useRunnerGroupsVisibility = true, set up the webhook, etc.
3. Create 1 runner deployment in the "general-dev" runner group with hra (1 to 5). Use "general-dev" label
4. Create 1 runner deployment in the "test-dev" runner group with hra (1 to 5). Also use "general-dev" label
5. Give your test Organization access to only the "test-dev" runner group
6. Create a workflow and specify run-on: "general-dev"
7. Execute the workflow n times

Describe the bug

As the test organization only has access to the "test-dev" runner group, the test dev runners shoud be scaled up.
Instead, the general-dev runners are scaled up:

(ignore the general-win-dev runners)

Workflows are processed 1 by 1 by the single test-dev pod.

The payload of the webhook show the correct runner group

Describe the expected behavior

"test-dev" pods would scale up and workflows would be processed in parallel

Controller Logs

-

Runner Pod Logs

-

Additional Context

No response

No source file or test is identified. Start by reproducing the runner-group setup and inspecting the webhook payload alongside controller scaling behavior; done means workflows targeting general-dev cause the accessible test-dev runners to scale in parallel, without scaling general-dev runners.