Issue Summary

When selecting a team in the component's Owner field dropdown, if multiple teams (managed and unmanaged) share the same name, the UI does not return or associate the correct team. This results in incorrect or ambiguous team assignments.

The root cause appears to be inconsistent behavior between the APIs used by different parts of the UI:

The Team selection UI uses the following GraphQL API, which targets Compass teams:
https://<YOUR-DOMAIN>.atlassian.net/gateway/api/graphql?operation=compass_team_searchTeams

The Component Owner field, however, uses a separate REST API to search teams:
https://<YOUR-DOMAIN>.atlassian.net/gateway/api/v4/teams/search

The REST API used by the Component Owner UI seems to ignore the team (managed) that shares its name with another and instead returns only the first match it finds. This inconsistency leads to the wrong team being displayed and selected when teams have identical names.

Steps to Reproduce

1. Create or ensure multiple teams exist with the same name. Test - managed team and Test - unmanaged team
2. Navigate to the component configuration screen.
3. Open the team selection dropdown.
4. Select a team with a duplicate name.

Expected Results

The correct team (based on ID or intended context) is selected and associated with the component.

Actual Results

An incorrect team is associated, or the dropdown behaves inconsistently due to name duplication.

Workaround

Change the name of one of the teams named "Test" - (unmanaged) to a distinct and unique name. Once renamed, refresh the page and try assigning the remaining "Test" - (managed) team to the component again. This should help avoid the conflict caused by duplicate team names.