feat: Support rule type code_scanning

[ihor-hrytskiv]

Support rule type code_scanning for github_organization_ruleset and github_repository_ruleset

Resolves #2310

Example:

data "github_repository" "workflow_repo" {
    name = "workflow_repo"
}

resource "github_organization_ruleset" "org_ruleset" {
    name        = "example"
    target      = "branch"
    enforcement = "active"

    rules {
        required_code_scanning {
            required_code_scanning_tool {
                alerts_threshold          = "errors"
                security_alerts_threshold = "high_or_higher"
                tool                      = "CodeQL"
            }
        }
    }
}

resource "github_repository_ruleset" "repo_ruleset" {
    name        = "example"
    repository  = data.github_repository.workflow_repo.name
    target      = "branch"
    enforcement = "active"

    rules {
        required_code_scanning {
            required_code_scanning_tool {
                alerts_threshold          = "errors"
                security_alerts_threshold = "high_or_higher"
                tool                      = "CodeQL"
            }
        }
    }
}

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

---

[kfcampbell]

@ihor-hrytskiv would it be possible to split out the google/go-github v66 upgrade to a separate PR? It makes it easier to roll back if something goes wrong with either part of the change, which we've had happen before.