Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue

### Dependency
- #4423

### Issues Created
- [x] #4423
- [x] #4506
- [x] #4508
- [x] #5476
- [x] #5477
- [x] #4509
- [x] #4510
- [x] #5587
- [x] #6199
- [x] #6242

### Overview
We need to create a plan and issues for changing from `good second issue` label to `good first issue` label, so that it all gets rolled out at once

### Action Items
- [x] Change all the closed issues and PRs to use the `good first issue` label instead of the `Complexity: Good second issue`
- [ ] Define and write all the issues required for this roll out plan (all the issues will get dependencies defined below)
- [x] Finding all the locations https://github.com/hackforla/website/issues/4423
- [x] Updating the code (includes contributing file, so this might require multiple issues) https://github.com/hackforla/website/issues/4506
- [x] Updating the wiki with new information (this might make require several issues) https://github.com/hackforla/website/issues/4508
- [x] #5476
- [x] #5477
- [x] Updating the Project Board, `Onboarding infos/links` column (there could be two tasks here, once to add a card that explains the change and changing the card(s)
- [x] https://github.com/hackforla/website/issues/4509
- [x] https://github.com/hackforla/website/issues/4510
- [x] Updating open PRs text if they need it (if after reviewing the PRs found in 4423 and none need updates to any text inside them, this checkbox can get checked and strike though)
- [x] ~Making the label change on issues https://github.com/hackforla/website/issues/4431 and adding a note to any issue that has an assignee.~ No open PRs or Issues with `good second issue` so 4431 was closed.
- [x] Making the label change on PRs (open and closed) and adding a note to all the open PRs
- [ ] Decide in which order the issues get done, or hold a PR party on a Thursday night to do all the issues at once with the team members.
- [x] Update all the closed Issues and PRs again to use the `good first issue` label instead of the `Complexity: Good second issue`
- [ ] If the issues are going to get done in a certain order (not a party), then edit each issue's dependency to represent the order.
- [ ] Update our Data Scientist that this change has been fully implemented https://github.com/hackforla/website/issues/4152#issuecomment-1499468391

### Resources/Instructions
Dependency for all the issues
```
### Dependency
- [ ] #4423
- [ ] #4432 is ready for implementation
```

Message that should go on PR issue. See issue 4423 for example
```
Hi, we are about to change the label on your PR `Complexity: Good second issue` to `good first issue` to relect the update to our issue ladder of all members will work on two good first issues instead of the dev team making seperate issues for first and second (even though they were essentially the same).

You might be asking youself, why do you need to do two good first issues, instead of just one?!. The first two issues is where we catch if anyone has problems with branching appropriately on our project. So we intentionly make them very very small and perscriptive so that we can focus on making sure you have the branching down before we move you on to the bigger issues that get less and less perscriptive as you go up the ladder.

When you sucessfully finish with this issue/PR, you can go on to a Small issue just as you would have before.
```
- [HfLA Site Audit: Good Second Issue Label](https://docs.google.com/spreadsheets/d/1xoCOAxoUXo2kVNeaQAwUgfqlNU0RiLGcHrY6sAGqhfc/edit#gid=0)