Update community facing documentation around workshops

[agoose77]

Context

Historically, 2i2c have run workshops in a fairly one-directional, low-bandwidth manner, e.g.:

• Community: we would like a workshop on these dates with these profiles
• 2i2c: great — it's ready

In fact, workshop preparation is much more complex than this. We need to understand what is being asked of us in order to be able to give the workshop a green light. We've suffered incidents (such as Earthscope's recent workshop), or narrowly missed them (AWI-CIROH) due to poor models of the infrastructure usage.

Why is this important?

We cannot expect our communities to fulfill the roles of cloud infrastructure administrators. It follows that we need to ensure that our process supports our communities in building towards a successful workshop in a scalable way — if we have three concurrent workshops in preparation, we need to be able to support that.

This is important both for community satisfaction — a successful workshop is a good outcome! — and for empowering our communities and staff by clarifying a vague or confusing process.

Definition of Done

Note

This is not yet specified.

[GeorgianaElena]

Closing this in favor of the more specific tasks in #8484