Automating the notification of 2FA compliance and setting repository membership to public

### Overview
New volunteers join hack for LA and do not finish their account setup.

### Current State
When I add new people to the github account for a team, I usually go through the roster, and check everyones status, and then slack message the ones who have 2FA disabled or membership marked private. This is not efficient, it leaves some teams unchecked entirely.

### Future Development
#### Github path
- [ ] Reviews all users once a week
- [ ] Identifies who has 2FA disabled
- [ ] Identifies who has membership marked private
- [ ] Opens issues on the repositories they have access to
- [ ] Adds issues to project board's prioritized backlog
- [ ] assigns the issue to them
#### VRMS path
- [ ] Reviews all users once a week
- [ ] Identifies who has 2FA disabled
- [ ] Identifies who has membership marked private
- [ ] emails them and the project managers on the projects they are on
- [ ] adds the requirement to pm management screen
- [ ] keeps track of how many times team member has been notified.
- [ ] when it reaches some pre determined threshold, rolls up to a admin report for action

### Action Items
Determine if the github API can be used for this activity, or a combination of git script and github actions to automate.

### Resources/Instructions
https://github.com/orgs/hackforla/people?utf8=%E2%9C%93&query=two-factor%3Adisabled

Mark your own membership public
https://help.github.com/en/articles/publicizing-or-hiding-organization-membership#changing-the-visibility-of-your-organization-membership

Setup two factor authentication on your account
https://github.com/hackforla/governance/issues/20