Include TigeraStatus objects state in the calico-ready unit checks

The goal of this issue is to include TigeraStatus objects state as part of the checks done inside calico-ready unit, giving the users a better feedback about Calico state when deploying/updating clusters.

As it was seen in Tigera operator ippool issue, after applying some changes on calico helm values inside values.yaml, changes are not propagated to Calico Installation CR, but are not actually implemented.

But calico-ready unit is reporting ready state:

 ✓ Kustomization/calico-ready - Resource is ready

Although ippool AVAILABLE status is False, giving the wrong impression to the users that change was successfully implemented.

$ k get tigerastatus
NAME      AVAILABLE   PROGRESSING   DEGRADED   SINCE
calico    True        False         False      14h
ippools   False       False         True       31s

$ k get tigerastatus ippools -o yaml
apiVersion: operator.tigera.io/v1
kind: TigeraStatus
metadata:
  creationTimestamp: "2025-12-10T21:18:42Z"
  generation: 1
  name: ippools
  resourceVersion: "915975"
  uid: fdfb0a4c-ecdc-47a4-adc8-a1d9dd99a4e9
spec: {}
status:
  conditions:
  - lastTransitionTime: "2025-12-11T11:59:57Z"
    message: 'Unable to modify IP pools while Calico API server is unavailable: '
    observedGeneration: 9
    reason: ResourceNotReady
    status: "True"
    type: Degraded
  - lastTransitionTime: "2025-12-11T11:59:57Z"
    observedGeneration: 9
    reason: Unknown
    status: "False"
    type: Available
  - lastTransitionTime: "2025-12-10T21:18:47Z"
    observedGeneration: 9
    reason: Unknown
    status: "False"
    type: Progressing