Provide more information on the .status.condition field

[git-hyagi]

Describe the solution you'd like
The architecture of Pulp operator and the components that it deploys is kind of complex. Not everyone knows all the components involved nor the order in which they are deployed.

To help troubleshoot the operator state, we could modify the .status.condition of Pulp CR instance:

• based on resource (deployment/sts) status
• based on pod logs

Example of issue that it could have helped:

• During a pipeline execution, molecule failed its execution and we don't know in what step it was and what it was trying to do:

  TASK [Wait 15m for reconciliation to run] **************************************
  fatal: [localhost]: FAILED! => {
      "api_found": true,
      "attempts": 150,
      "changed": false,
      "resources": [
...
              "status": {
                  "conditions": [
                      {
                          "lastTransitionTime": "2022-06-02T21:26:54Z",
                          "reason": "",
                          "status": "False",
                          "type": "Successful"
                      },
                      {
                          "lastTransitionTime": "2022-06-02T21:40:46Z",
                          "reason": "Running",
                          "status": "False",
                          "type": "Running"
                      },
                      {
                          "lastTransitionTime": "2022-06-02T21:40:57Z",
                          "reason": "Failed",
                          "status": "True",
                          "type": "Failure"
                      }
                  ]

The idea is to, instead of just providing that operator failed or was in a running state, provide the status of each Pulp operator component with a descriptive message. Here is an example of an expected output:

              "status": {
                  "conditions": [
                      {
                         "type": DB-Available,
                         "message": Database Running,
                         "reason": DatabaseReady,
                         "status": "True",
                         "lastTransitionTime": "2022-06-02T21:40:46Z"
                      },
                      {
                         "type": Pulp-Api-Available,
                         "message": Pulp Api Not Running,
                         "reason": PulpApiNotRunning,
                         "status": "False",
                         "lastTransitionTime": "2022-06-02T21:40:46Z"
                      },
                      {
                         "type": Pulp-Content-Available,
                         "message": Pulp Content Not Running,
                         "reason": PulpContentNotRunning,
                         "status": "False",
                         "lastTransitionTime": "2022-06-02T21:40:46Z"
                      },
...
                  ]

Here is an example of dns cluster operator from OpenShift:

status:
  conditions:
  - lastTransitionTime: "2022-06-06T14:23:26Z"
    message: DNS "default" is available.
    reason: AsExpected
    status: "True"
    type: Available
  - lastTransitionTime: "2022-06-06T14:23:26Z"
    message: desired and current number of DNSes are equal
    reason: AsExpected
    status: "False"
    type: Progressing
  - lastTransitionTime: "2022-06-06T14:23:26Z"
    reason: DNSNotDegraded
    status: "False"
    type: Degraded