Remove unused status.clusterStatus

[ChunyiLyu]

This closes #636

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

Summary Of Changes

• remove unused rabbitmqCluster.status.clusterStatus from cluster status

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]

May I suggest, as part of this PR, replace (instead of remove) cluster status with some other print columns?

I was thinking of exposing perhaps AllReplicasReady and ReconcileSuccess?

I think that if we just remove, out kubectl get rmq output won't provide much information. I'm ok too if you want to implement the printing columns as part of another story/PR.

Last thing, perhaps is time to do a go mod tidy? We have some dependencies declared 3 or 4 times 🙈

[ChunyiLyu]

@Zerpet status.clusterStatus is empty and not set. If you list rabbitmqCluster now (without this change), it looks like

NAME     AGE   STATUS
sample   3s

Deleting status.clusterStatus is not removing any currently available information from our users. We can certainly print additional information in in the column, but sounds like a different PR to me.

[Zerpet]

I'll create an issue to add additional printing columns 👌