Description of the new feature/enhancement

I know that there could be a decent amount of effort involved in this for a repos with such a large footprint, but I think there's no time like the present to "commit" ourselves (oh god the pun! the 🔥) to (seriously) Doing Better as people, developers, and as global citizens.

I propose renaming the current master branch to main as an acknowledgement of the community's commitment to recognizing the existence of racial injustice. However small or trivial an act it may seem to some, I feel that it's a worthwhile undertaking.

As a phrase I'm oft known to cite goes, "excellence is a game of inches".

The IETF presents a detailed discussion of the reasons why this it is important to note the terminology of branch names, and should be considered a highly useful resource for basing any discussions around context, pertinence, or applicability.

Proposed technical implementation details (optional)

Just spitballing OTOMH the things that might be considered as part of executing on this. Obviously, whomever does this would need to have appropriate repos perms :)

0. Coordinate with any dependent repos' owners on logistics/timing(if needed) ❓
1. Disable CI/CD pipelines and PR bots
2. Create main branch via operation with master checked out via git branch -m master main (note the -m to keep history intact)
3. Push to main origin
4. change default branch in GH from master to main
5. Configure main branch protection, security, etc rules in GH
   5a. Archive/lock or otherwise deprecate master branch
6. Re-Enable CI/CD, test/adjust build scripts (if/as needed)
7. Notify downstream repos ❓