Issue a warning when adding a repo for an organization that has not set a GitHub org in the PMI

When a project has no GitHub org set in the PMI, adding a new repo will not automatically set the permissions via the sync script. The repo has to be added explicitly to the PMI under section GitHub repositories.

Special case for now is adoptium, where the GitHub org is for the umbrella project, but individual repos are for individual child projects, like temurin.

The set of teams that will be setup to access the repo is different, so we should add a warning in the apply operation that you have to add this created repo to the PMI for the permissions to be setup correctly afterwards.