Bug: PersistentVolumeClaim reconciliation blocks until usage by another resource

Currently we consider a PVC to be Current when its phase becomes `Bound`. But this means that if a PVC ends up in an earlier group than the Deployment/Statefulset that uses the PVC (because of mutations or depends-on), then it will not reach Current status.
Alternatively, we can try to determine which workloads is using the PVC, and then in the solver make sure that they always end up in the same group.

Start by tracing PVC reconciliation and the solver behavior described in the issue, using a PVC alongside a Deployment or StatefulSet whose ordering is affected by mutations or depends-on. Reproduce the case where the PVC remains non-Current, then verify that reconciliation reaches Current without blocking on the workload ordering.

Written by the indexing model from the issue text.