Add rabbitmq.com/disable-default-topology-spread-constraints annotation

[DanielDorado]

When the annotation rabbitmq.com/disable-default-topology-spread-constraints is set to "true", the default topologySpreadConstraints based on label topology.kubernetes.io/zone is omitted.

As @Zerpet suggested in issue #1687, I added the annotation to skip the default topology constraint configuration because the override was not working as expected ( #1690 ), and @mkuratczyk was not satisfied with the behavior.

This closes #1687

Note to reviewers: Remember to look at the commits in this PR and consider if they can be squashed

Summary Of Changes

When a user adds the annotation rabbitmq.com/disable-default-topology-spread-constraints: "true" in their RabbitMQCluster custom resource, the default topology spread constraint is omitted.

Additional Context

Local Testing

Please ensure you run the unit, integration and system tests before approving the PR.

To run the unit and integration tests:

$ make unit-tests integration-tests

You will need to target a k8s cluster and have the operator deployed for running the system tests.

For example, for a Kubernetes context named dev-bunny:

$ kubectx dev-bunny
$ make destroy deploy-dev
# wait for operator to be deployed
$ make system-tests

[Zerpet]

@DanielDorado the code changes look good. Can you rebase this PR on top of main ?

I just fixed our CI, and GitHub Actions picks the workflow file from the branch-off commit (that has a broken CI).

[DanielDorado]

@Zerpet done.

[Zerpet]

I did the following QA:

• Deploy with the annotation ✅ deploys without the default spread constraint
• Deploy with annotation + override ✅ deploys with just the spread constraints in the override
• Deploy without the annotation + override ✅ deploys with both, the default and the override

[Zerpet]

Thank you!