[Self-Hosted] Guidance on workspace resource limits for Reference Architectures.

[lucasvaltl]

Is your feature request related to a problem? Please describe

Currently we do not give guidence on setting limits for workspace sizes - we only set a default request (which is here afiak).

Describe the behaviour you'd like

In order to avoid any future complexities around this, we should more clearly set a default limit in the reference architectures, explain the impact of this and how to change it, and also explain what impact it has on the number of workspaces per node (in combination with the request set). This should be implemented for all existing reference architectures.

Describe alternatives you've considered

• Do nothing - which will likely result in a bad experience over time

Additional context

• this is a follow up for a comment raised in this PR
• This relates to Epic: Workspace Classes on Self-Hosted #10805 , where we are likely to create a better UX for setting workspace sizes.
• Internal discussion

[aledbf]

Currently we do not give guidence on setting limits for workspace sizes

This should be implemented in the current alpha, not even in beta. Delaying this until alpha means customers in production are exposed to node issues (loss of nodes and content), bad performance, and noisy neighbors.

ping @csweichel