Setup

• Rancher version: v2.13-head
• Rancher UI Extensions:
• Browser type & version: Version 140.0.7339.186 (Official Build) (arm64)

Describe the bug

When setting the option for Configure who should be able to login and use Rancher to either Allow members of cluster/projects plus authorized users & groups or Restrict access to only authorized users & groups options, the search bar does not automatically show the teams/orgs a user belongs to. Also, once a user/team/org has been selected the option to save is greyed out and doesn't actually save what is selected unless you click Edit config and re-enable the auth provider.

To Reproduce

1. Deploy Rancher on v2.13-head
2. Enable Github App auth provider
3. Select either Allow members of cluster/projects plus authorized users & groups or Restrict access to only authorized users & groups option for configuring login
4. Click into the Add Member search bar and observe the teams/orgs the user belongs to do not appear automatically
5. Search for a user/team/org and select them
6. Observe the Save button is greyed out and you cannot select it
7. Refresh the page (or navigate away from this page and return) and observe the selection for Configure who should be able to login and use Rancher has been set back to Allow any valid user.
8. Repeat step 5
9. Click Edit config and re-enable the auth provider
10. Observe that Configure who should be able to login and use Rancher is set to the option chosen in the previous step and the selected user/team/org appears
11. Observe that when clicking in the Add Member search bar the teams/orgs the user belongs to appear automatically

Result
You cannot save the configuration of authorized users and groups and have to edit the config and re-enable the auth provider in order to save the results. Also the teams/orgs the user belongs to do not appear in the search bar automatically initially, but they do upon re-enabling the auth provider.
Expected Result

The teams/orgs the user belongs to should appear automatically in the search bar and you should be able to select either option for Configure who should be able to login and use Rancher and save the results instead of having to edit the config and re-enable the auth provider.

Screenshots

Additional context
Related to rancher/rancher#50517