Repository creation for org members is enabled by default and leads to permission inconsistencies

Created by: fredg02

Repository creation for organization members seems to be enabled by default, when a new org is created. Here are a few examples

• https://github.com/organizations/eclipse-iofog/settings/member_privileges
• https://github.com/organizations/eclipse-openj9/settings/member_privileges
• https://github.com/organizations/eclipse-embed-cdt/settings/member_privileges
• https://github.com/organizations/eclipse-emfcloud/settings/member_privileges
• https://github.com/organizations/eclipse-glsp/settings/member_privileges

When members create repos, they are not added in PMI and therefore are not considered during a GitHub sync script run. This leads to missing teams (-committers, -contributors, -project-leads) and committers having admin rights on projects (since they have created them).

If possible, we should check that this option is disabled and disable it if it's not through the API.

Related question: What do we do with existing repos that were created by members? Do we let the project leads confirm that they are legit and add them to the PMI manually?