feat: adds new branch protection options for last reviewer and locking branch

[wwsean08]

Resolves #1352 (at least for the v4 version of branch protection)
Resolves #1341 (at least for the v4 version of branch protection)

Behavior

This enables two new options introduced in October around branch protections, specifically, the ability to require the last approval be from someone besides the last person to push to the branch (for the case that multiple people are working on the same branch), as well as the ability to lock branches.

The new option did require upgrading shurcooL/githubv4.

Before the change?

• This can't be changed via terraform

After the change?

• These options are available for managing the state of these branch protection options

Other information

• N/A

---

Additional info

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)
• Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Type: Feature

---

Manual Testing:

Overrode terraform to use by locally built version via dev.tfrc, and these were the results (with repo/org names redacted):

main.tf:

terraform {
  required_providers {
    github = {
      source  = "integrations/github"
      version = "~> 5.0"
    }
  }
}

data "github_repository" "test" {
  full_name = "REDACTED/REDACTED"
}

resource "github_branch_protection" "example" {
  repository_id = data.github_repository.test.node_id
  pattern = "test"

  required_pull_request_reviews {
    require_last_push_approval = true
  }

  lock_branch = true
}

Branch protection rules created (in two screenshots because of the size of the page)

[wwsean08]

Note I would have added the feature label, but don't have the ability to

[kfcampbell]

Thank you for the contribution and thoughtful manual testing description!

Integration tests here are broken on main and the changes in this PR do not cause any new breakages.