Define per-repository configuration settings

Adoptium currently has 47 repositories for various tasks. This issue is to define the expected settings for these repositories to ensure they are secure, allow people to be productive, and are consistent to avoid surprises.

Repository settings include such items as:
- branch protection
- access control lists (alignment with [Eclipse requirements](https://www.eclipse.org/projects/handbook/#resources-github-access)), and removing temporary `admin` access rights
- required number of PR approvers
- constraints on forced push
- _etc_

First step is to define the expected settings for each type (infra, dev code, release repo, website/api, etc) of repository we handle. Second step is to bring the 47 repositories in line with these settings - which may require temporary admin access.

Start by inventorying the 47 repositories and grouping them into the stated types: infra, dev code, release repo, and website/API. Define the expected branch protection, access control, approver, and forced-push settings for each type, then bring every repository into line; done means the settings are documented and consistently applied.

Written by the indexing model from the issue text.