Update git flow convention in documentation

[mreeve-snl]

🗣 Description

Adds new branching convention to releases/contributing docs.

💭 Motivation and context

We have 2 main branches whose names will stay constant:

1. The main branch tracks Major/Minor/Patch releases only, and is only updated with merges from the develop or a hotfix branch. Releases are tagged appropriate SEMVERs based on their content: vX.Y.Z.
2. The develop branch is our working copy of latest changes, and tracks all feature development. Feature branches are merged into develop as features are added, and when ready develop will merge into main as documented above.

There are 2 other branch naming conventions that change based on the issue/update/content they add to the project.

1. A hotfix branch is created to "fix" or "patch" a critical issue in the main branch of the LME repository. Hotfixes are branched from main and merged into develop. This way main can get fixes, and develop will be synced with main.
   - It uses the convention: hotfix-<username>-<issue#>-<shortstring>
   - An example: hotfix-cbaxley-222-fix-the-pipeline
2. A feature branch is created from develop to add content for issues/work/updates/etc...
   - It uses the convention: -<issue #>-shortstring
   - An example: mreeve-22-filter-events

NOTE: Each branch name will have a short string to describe what it is solving for example create-new-container:

📷 Screenshots (DELETE IF UNAPPLICABLE)

🧪 Testing

Displays properly on github wiki.

✅ Pre-approval checklist

• Changes are limited to a single goal AND
  the title reflects this in a clear human readable format
• Issue that this PR solves has been selected in the Development section
• I have read and agree to LME's CONTRIBUTING.md document.
• The PR adheres to LME's requirements in RELEASES.md
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.

✅ Pre-merge Checklist

• All tests pass
• PR has been tested and the documentation for testing is above
• Squash and merge all commits into one PR level commit

✅ Post-merge Checklist

• Delete the branch to keep down number of branches

[mitchelbaker-cisa]

Overall looks good. Added a couple links to RELEASES/CONTRIBUTING docs and had some questions on how we want to handle hotfixes.

[Roger-CISA]

Thanks Mikey and Mitchel, no edits from me.

[mreeve-snl]

https://github.com/cisagov/LME/blob/hotfix-mreeve-523/RELEASES.md

OK @mitchelbaker-cisa I think all your comments are covered in the new changes I'm pushing... let me know, and I'll let you or roger go ahead and merge this

it also looks like the linux test is still having issues, but hopefully we can get that fixed up soon :)

[mitchelbaker-cisa]

Thanks Mikey! Now that I'm thinking about it, we could automate the post merge step if we wanted to.. maybe something we can add to our pipeline later on.

https://stackoverflow.com/questions/67668006/how-to-automatically-merge-a-branch-into-another-in-github
https://github.com/marketplace/actions/action-automerge