Add sizing recommendations for workshop portals in production

[mocdaniel]

Is your feature request related to a problem? Please describe.

Right now, there is very little information in the documentation regarding (right)sizing production platforms.

There exists a great sections about available resource quotas for workshops, but there don't seem to be any guidelines regarding node count or expectable resource usage for different meta types of workshops.

Describe the solution you'd like

While I understand that resource usage and thus sizing of environments comes down to the workshops ran on the platform, I would love to see some general recommendations based on observations and experiences with workshops held, e.g. for those workshop classifications:

• lightweight workshops with isolated namespaces (Kubernetes 101, Deploy your first pod, what are services?)
• workshops with dedicated vClusters (RBAC concepts, cluster networking, lightweight controllers)
• workshops with dedicated vClusters and heavy load (build your own IDP, GitOps with ArgoCD, running Rook on Kubernetes)

Describe alternatives you've considered

I think documentation like this needs to grow over time. A good thing would be a CTA on Slack/the project's README for people to tell the maintainers about their own experiences and observations regarding sizing of workshop environments.

Additional information

Slack thread for reference

[GrahamDumpleton]

Will possibly be in part covered by some old non public docs are adding in #312. At least will be a good start.