Problem

When inviting an external client to a team in Ploi, that client can currently see all connected source control providers (e.g. GitHub repositories) belonging to the account owner. There is no option to hide or restrict visibility of source control providers on a per-team basis.

Requested features

1. Source control provider visibility toggle per team

Add a setting in the team configuration that allows the team owner to disable the visibility of connected source control providers for members of that team. This prevents external clients from browsing repositories they have no business accessing.

2. Attach source control providers to specific teams (like server providers)

Implement the same "attach provider to team" model that currently exists for server providers — allow account owners to explicitly assign which source control providers are available within a given team. This gives fine-grained control so client teams only see what they need.

Use case

Agencies and freelancers managing external client teams in Ploi need to be able to isolate what each client can see. Clients should only have visibility into resources relevant to their own project — not the provider's entire GitHub organisation or other clients' repositories.

Suggested UX reference

Mirror the existing Attach server providers flow — apply the same pattern to source control providers, so the experience is consistent and familiar to existing Ploi users.