Docs Request: Explain the Contributing/Release approach, and switch to a standard git workflow

[parker-research]

It seems like the beta branch is diverging from the main branch. Would be helpful to explain whether people should be forking and building from beta or main. The latest release (tag 2603242) appears to have come from the beta branch has release notes that contain PRs all to the beta branch, but is marked as stable.

My suggestion is to switch to a standard git workflow:

1. Merge the beta branch to main once at the start, and remove the beta branch.
2. Do development in the main branch.
3. When considered stable, make a release from main.
4. If you need to patch something from the latest stable release, but without including the in-progress "beta" changes (i.e., a hotfix), you make a new branch based on the latest stable release, make your hotfix, and push that as a release.