Documenting procedure for adding "beta" deployments, or promoting deployments out of beta

[scottisloud]

This PR provides documentation about what are currently called "Beta" deployment examples. With this, I hope to:

• Reduce confusion among users of this repository about what "beta" means by describing what is actually in "beta" (e.g., the deployment method, not the application itself).
• Provide clear criteria and process for adding beta deployment examples to ensure consistency and improve reproducibility over time.
• Provide clear criteria and process for promoting beta deployments out of beta.

In it's current form, this PR merits considerable discussion and refinement. Specifically:

• Is the documentation too comprehensive? Should it be simplified?
• I picked numbers out of the air for the number of customers who must use the deployment example to qualify for promoting out of beta.
  • What numbers actually make sense here?
  • Is a number actually required or is this a "you'll know it when you see it" situation?
• Are the processes for adding or promoting beta examples clear enough?

I'd love for this to be absolutely shredded, ripped apart, and rebuilt to be really great. There is a lot of subjectivity and discretion with all of this so I am attached to no part of what I've written in this first complete draft.

[scottisloud]

After many discussions we will be sticking with the Beta label.

I've made some minor tweaks to reduce the specificity of the criteria. It's not possible to provide specific criteria that will work in all circumstances, so a "you'll know it when you see it" approach is probably the best way forward.

Looking for feedback on quality of the copy, the processes outlined (e.g., are they reasonable, clear, etc).

[scottisloud]

Alrighty all feedback addressed, merged very recent changes from main in. Would love a re-review.