Review if/how to document any requirements for Anti-Affinity-enabled components

[conceptualshark]

The SM platform architecture documentation originally included these considerations:

• By default, the deployment requires at least three Kubernetes Nodes to meet the Pod Anti-Affinity constraints.
• For components with Anti-Affinity enabled, like Zeebe Broker, the Kubernetes Nodes should be equal to or greater than the number of the Pod replicas. Otherwise, some of its Pods will not be scheduled and will be in a "Pending" state.

This page was removed and revamped to a less-technical section of the overview, and these points were removed. They were already out of place and not discussed in-depth anywhere else in the guides, and warrant a deeper discussion/understanding of intent, to evaluate and document them more completely.

See #4049 (comment)