add some pod status to the cr status deployed condition for starting pods

[gtully]

If a broker pod for some reason does not start, our deployed condition tells us 0/1 pods ready, but nothing more.
querying the relevant pods and finding the pod status and reporting some of that in the message of the PodNotReady reason would greatly improve usability. One use case is where a storage class is not available, the pod status has the detail but the cr status does not have any relevant detail.
There is obvious duplication here, but when a pod is starting, and the Cr operator is waiting for started, there is interesting information to share.

[gtully]

This sort of thing:

CR Status:{[{Valid True 1 2024-09-10 16:21:28 +0100 IST ValidationSucceded } {...} {Deployed False 0 2024-09-10 16:21:28 +0100 IST PodsNotReady 0/1 pods ready, {aa-rwm-pvc-ha48a-peer-a-ss-0: Pending [{PodReadyToStartContainers=True :}{Initialized=False ContainersNotInitialized:containers with incomplete status: [aa-rwm-pvc-ha48a-peer-a-container-init]}{Ready=False ContainersNotReady:containers with unready status: [aa-rwm-pvc-ha48a-peer-a-container]}{ContainersReady=False ContainersNotReady:containers with unready status: [aa-rwm-pvc-ha48a-peer-a-container]}{PodScheduled=True :}]}} {Ready False 0 2024-09-10 16:21:28 +0100 IST WaitingForAllConditions Some conditions are not met}] {[] [aa-rwm-pvc-ha48a-peer-a-ss-0] []} ...

augment the PodsNotReady message.