Add support to Allow specified actors to bypass pull request requirements

[jtyr]

The provider is missing option to "Allow specified actors to bypass pull request requirements" in the branch protection rule settings.

# Settings -> Branches -> <ProtectionRule> -> Protect matching branches:

|X| Require a pull request before merging
    |X| Allow specified actors to bypass pull request requirements
        <ListOfTeamsOrUsers>

[jtyr]

There is no support for this in the google/go-github package and neither this feature is documented in the official GitHub REST API 😞

[majormoses]

It looks like they added support for it in GraphQL API: https://docs.github.com/en/graphql/reference/input-objects#updatebranchprotectionruleinput it looks as if we need to pass bypassPullRequestActorIds with an array of ids.

[jtyr]

As soon as the githubv4 package supports this feature, we will be able to add it into this provider. I guess the author of githubv4 must regenerate the code from the latest GitHub GraphQL schema.

[jtv8]

#1030 is now merged and looks to be available as pull_request_bypassers in the provider: https://registry.terraform.io/providers/integrations/github/latest/docs/resources/branch_protection#required-pull-request-reviews - should this issue be closed now?

[chenshap]

is it planned to be added to github_branch_protection_v3?
https://registry.terraform.io/providers/integrations/github/latest/docs/resources/branch_protection_v3

[github-actions]

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!

[kfcampbell]

I'm going to close this issue as pull request bypassers are implemented in the non-v3 resource. @chenshap it's still an outstanding need to add this functionality to the v3 version of the resource, though it's still not available in google/go-github. It is, however, exposed in the REST API. Please feel free to create another issue to track that work if you'd like!