Add methods to add and remove repos for actions on org level

[FloThinksPi]

This commit adds the abillity to add one or more repositories to the
list of enabled repositories for github actions on org level.
It also adds the abillity to remove them from this list.
With this change we can now enable and disable repos to use github actions on org level.

The used endpoints for this are:
https://docs.github.com/en/rest/reference/actions#set-selected-repositories-enabled-for-github-actions-in-an-organization
https://docs.github.com/en/rest/reference/actions#disable-a-selected-repository-for-github-actions-in-an-organization

fixes #1995

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[codecov]

Codecov Report

Merging #1997 (8351b36) into master (465df60) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1997   +/-   ##
=======================================
  Coverage   97.86%   97.86%           
=======================================
  Files         107      107           
  Lines        6871     6897   +26     
=======================================
+ Hits         6724     6750   +26     
  Misses         81       81           
  Partials       66       66           

Impacted Files	Coverage Δ
github/actions_runners.go	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 465df60...8351b36. Read the comment docs.

[gmlewis]

Thanks, @FloThinksPi , but this PR appears to have a few problems.
Did you try out these two new methods before submitting the PR?

I ask because one of the signatures doesn't match the official documentation and I'm not sure how it could have worked.

[FloThinksPi]

Woh thanks @gmlewis for the super quick review.
I just wanted to display the diff and must have opened it already. Didnt run it yet at all, just the tests.
I will include your suggestions and try it out.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[FloThinksPi]

@googlebot I signed it!

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[gmlewis]

Hi @FloThinksPi - it looks like the tests need updating:

=== RUN   TestActionsService_AddEnabledReposInOrg
    actions_runners_test.go:411: request Body is {"selected_repository_ids":[123,1234]}
        , want {"repository_id":[123,1234]}
--- FAIL: TestActionsService_AddEnabledReposInOrg (0.00s)

[gmlewis]

@googlebot I consent.

[FloThinksPi]

@gmlewis Yea all done now 👍🏼 . I also renamed the AddEnableReposInOrg method to SetEnabledReposInOrg since the used endpoint sets the list absolute. I thus added the https://docs.github.com/en/rest/reference/actions#enable-a-selected-repository-for-github-actions-in-an-organization endpoint which is now AddEnableReposInOrg which appends to the list of enabled repos.

All tests return ok and i tested all three methods against a GitHubEnterprise 3.0 Instance.

Are you fine with the method names ?
Should i squash the commits ?

[gmlewis]

Should i squash the commits ?

You don't need to squash, as we only "Squash and merge" in this repo anyway.

I'll check the names now.

[gmlewis]

Thank you, @FloThinksPi !
LGTM.

Awaiting second LGTM before merging.

[gmlewis]

Thank you, @wesleimp !
Merging.