Resolves #2470

Before the change?

• Using a team slug for github_repository_collaborators would result in churn
• There is no way to manage repository collaborators for an organization that has organization roles defined without specifying these teams as part of the github_repository_collaborators resource (which works but is technically incorrect).

After the change?

• Using a team slug for github_repository_collaborators does not churn
• You can use the team_ignore block on a github_repository_collaborators resource to ignore organization managed teams.
  • Due to the lack of flag in the GitHub API this can't be cheaply powered by a ignore_org_teams resource flag, as that would take multiple API calls and an increase in required permissions.

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No