Outline a clearer process for CI releases with feature holding branches.

[cdcabrera]

Description

The PF4 updates have highlighted a limitation around pushing/merging changes in a linear CI <-> QA -> Stage -> Prod direction.

Outline a branching process that handles the not-so-great project one-off request.

Acceptance Criteria

• CONTRIBUTING.md has been updated

Assumptions and Questions

A few possibilities

1. Do nothing, maintain what we do today. If something is blocking an environment from moving forward we don't merge into said environment.
2. Feature holding branches, as the commits get approved and checked by QE they get merged into a holding branch that doesn't sync with any environment
3. Feature environment branches similar to ci-some-feature or qa-some-feature where the changes are continuously added into the branch and the environment, but remain separated at the source control level... actual CI. There may need to be some form of automation to help with rebasing changes

[cdcabrera]

Mostly resolved with ephemeral env workflow #956