Rework statuses for a Custom Resource

The output of kubectl get psmdb shows some statuses for PSMDB custom resource.

The status are not clear and sometimes broken.

This Improvement makes sure that we have the following statuses:

• Initializing
• Ready
• Paused
• Stopping

 

Stories are as follows:

• As a user, I expect to see CR state ready if all components are up and running
• As a user, I expect to see CR state paused if the cluster was stopped with ‘pause’ flag
• As a user, I expect to see CR state initializing if the cluster is provisioning or scaling
• As a user, I expect to see CR state Stopping if cluster is stopping or being deleted
• As a user, I expect to see CR state error if any uncaught exception happens inside the Operator. If errors happen in other components, initializing state should be used.
• As a user, I expect to see component statuses aligned with CR statuses