feat: Added organization role support

[stevehipwell]

Resolves #2314
Resolves #2224

---

Before the change?

• No support for organization org roles

After the change?

• Added support for organization or roles
• Data sources
  • github_organization_repository_role
  • github_organization_repository_roles
  • github_organization_role
  • github_organization_role_teams
  • github_organization_users
  • github_organization_roles
  • github_organization_security_managers
• Resources
  • github_organization_repository_role
  • github_organization_role
  • github_organization_role_team
  • github_organization_role_user

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

---

[jtnz]

JFYI I think that this will conflict with github_repository_collaborators and will need a note in the docs to warn users.

I tried this out today (manually assigned an org role to a team) and on the next TF apply run it proceeded to spend the next ~45mins trying to remove the team from every repo in the organization. It finished happily (and with no actual affect), but the next run it does the same thing. I believe the problem is in the GH API. It mashes all team access together and offers no way to differentiate why the teams are in the list ("direct access" vs "organization access").

[stevehipwell]

@jtnz github_repository_collaborators has an input to allow it to not conflict with organization roles; the docs likely should belong on github_repository_collaborators (check out #2551 where these are already being updated). This is a GitHub issue and not provider related, due to the way the API works there isn't an easy way to filter org role users out at the repo level.

[jtnz]

@stevehipwell Haha, yeah, I just found this in 6.5.0. Thanks