[SIG leads] Access control review

[justaugustus]

#2859 highlights the need for our annual access control review.
@kubernetes/sig-release-leads @xmudrii @katcosgrove — I'll be working with all of you to go through our areas and prune/update OWNERS, k/org teams, ensure GCP permissions are up-to-date, and our current, active personnel are listed in the right places.

We'll use this umbrella to also close out #2516 and #2515.

[justaugustus]

First part of this is in #2865 (primarily for the Release Team).

Follow-ups from that:

• Remove any references to build-admins group
• Update Release Team onboarding documentation to reference the correct OWNERS paths to update (cc: @drewhagen)

[justaugustus]

Update Release Team onboarding documentation to reference the correct OWNERS paths to update (cc: @drewhagen)

From Vyom in #2865 (comment):

Just so that it can be fixed after this PR is merged, this will require updates to the release lead template: (I won't cover it in my updates until this PR is merged)

sig-release/.github/ISSUE_TEMPLATE/release-team-lead-progress.md

Lines 45 to 51 in da16357

	- [ ] Updated `kubernetes/sig-release` `OWNERS`
	- Release Team Lead and Shadows
	- Add an `approvers` entry in `releases/release-1.XX/OWNERS`
	- **Release Team Lead only**
	- In `OWNERS_ALIASES`, add an entry in the following sections:
	- `release-team`
	- `release-team-lead-role`

@Vyom-Yadav — I'll let you handle that update now that #2865 has merged.
Feel free to unassign yourself from this issue once that is done.
/assign @Vyom-Yadav

[Vyom-Yadav]

Addressed that in dc01c50, which will be merged alongside other changes in #2866

/unassign

[justaugustus]

Addressed that in dc01c50, which will be merged alongside other changes in #2866

Thanks Vyom!

[drewhagen]

We had a few PRs merge prematurely because folks gave a loose approval.

See: #2860 and #2871

Do we expect that pruning/updating owners will help with this? If not, I will write up another issue.

@justaugustus