/kind feature
/assign

Describe the solution you'd like
Currently we have OSC.spec.managedSecurityGroups.AllNodesSecurityGroupRules. This is somewhat problematic because:

• users sometimes expect that bastion security groups should also be part of this (related ticket: Bastion security group rules dont get updated #2981)
• introduction of functionality to manage bastion security group rules would make it a bit weird

The intention is to just rename allNodesSecurityGroupRules to something more clear such as clusterNodesSecurityGroupRules (open to suggestions).
This will:

• clarify to users the scope of this field
• allow future addition of bastionNodeSecurityGroupRules without weird naming ( im personally interested in this feature but implementation of it has low-prio and will be outside of the scope of this issue, it can added in the future without breaking api changes afaik )