contributing guide needs branch guidance

[akaszynski]

We originally had branch guidance setup in

Branch Naming Conventions

To streamline development, we have the following requirements for naming branches. These requirements help the core developers know what kind of changes any given branch is introducing before looking at the code.

fix/: any bug fixes, patches, or experimental changes that are minor

feat/: any changes that introduce a new feature or significant addition

junk/: for any experimental changes that can be deleted if gone stale

maint/: for general maintenance of the repository or CI routines

doc/: for any changes only pertaining to documentation

no-ci/: for low impact activity that should NOT trigger the CI routines

testing/: improvements or changes to testing

release/: releases (see below)

Let's add that back in or include a reference to that.