Github guideline for branching and release process

[snarve]

🗣 Description

This issue covers documenting the Github guideline for branching strategy, issue creation and review process.

Closes #357
Closes #358
Closes #364

💭 Motivation and context

• Document a standard process for creating issues and reviewing PRs
• Maintain a branching strategy closely aligned with Gitflow for code and baseline updates during development and release process

🧪 Testing

• Review the Github guideline and Branching structure document
• Link to docs:
• https://github.com/cisagov/ScubaGoggles/blob/357-document-the-github-guidelines/DEVELOPMENTGUIDE.md
• https://github.com/cisagov/ScubaGoggles/blob/357-document-the-github-guidelines/BRANCHINGSTRUCTURE.md

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• The relevant issues PR resolves are linked preferably via closing keywords.
• All relevant type-of-change labels have been added.
• I have read and agree to the CONTRIBUTING.md document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[buidav]

initial comments