[enhancement] Moving levels versioning and roll out process

The TOC needs to document how we make changes to the moving levels criteria and versioning. We reported on this to the GB last quarter and need for capture this in our operations directory (i cannot find it which tells me it was a good idea we didn't write down).

This should cover all future changes to the criteria so the TOC, our projects, and community members understand what to expect as adopter needs and cloud native practices mature and evolve over time.

- **Moving Levels Criteria are versioned** - Versioning of the criteria is set at the full criteria list in the process, regardless of the maturity level. There is no dedicated criteria version for incubation, nor one for graduation. If the TOC changes criteria for incubation only, the entire criteria and process is updated to reflect this.
- **Criteria will not change versions more than once within the same calendar year**. It is anticipated that the TOC conduct criteria reviews at least every other year to ensure we're keeping pace with changes and advancements of projects applying to move levels, as well as reassess the effectiveness and value of the criteria and our projects' ability to implement and meet them.
- **Changes to criteria adhere to a public comment process** in accordance with the TOC's decision making to ensure opportunity and inclusion of community feedback
- **Any major/critical modifications and all additions are first categorized as "suggested" for each level.** Suggested criteria may remain suggested until the TOC reviews and affirms projects' ability to continuously meet them during the criteria review. Suggested criteria may be moved to required when (TBD: 60%) or more projects moving levels continuously meet it. Administrative and clarifying enhancements (modifications of the criteria for spelling, grammar, understanding, etc.) are not considered major/critical as they do not alter the intent of the criteria.
- **All project Due Diligence must record the version of the criteria** (historical reference in the event a decision needs revisited) for which the project was evaluated against. While the DD template for the TOC does capture the actual criteria at the version, we need to be able to point back to the official source in the event modification of the criteria for the DD is called into question. Any compensating mechanisms and the corresponding TOC evaluation statement should address deviations from the defined criteria and detail why a project did/ did not meet the criteria as written (this remains unchanged).

Start by locating the operations directory and existing Moving Levels criteria and Due Diligence documentation. Document the versioning, review, public-comment, suggested-criteria, and historical-reference rules described in the issue. Done means the process is captured in the operations documentation so the TOC, projects, and community can find it.

Written by the indexing model from the issue text.