Check restic daemonset for readiness on install

[nrb]

Currently, velero install --wait attempts to check the Deployment with the velero server for readiness, but does not look at the restic daemonset.

For completeness, it should also check to be sure the restic daemonset is in a usable state.

[skriss]

Here's an example of what I see in the status for a ready DaemonSet:

status:
    currentNumberScheduled: 3
    desiredNumberScheduled: 3
    numberAvailable: 3
    numberMisscheduled: 0
    numberReady: 3
    observedGeneration: 10
    updatedNumberScheduled: 3

Looking at the API documentation, I think we probably want to compare numberAvailable to desiredNumberScheduled.

[prydonius]

FYI this is how Octant checks the status of a DaemonSet: https://github.com/vmware/octant/blob/f3702d9a64ba228b4ffa1c81b37be34780b1cf47/internal/modules/overview/objectstatus/daemonset.go. Looks like if numberMisscheduled == 0 && numberAvailable == numberReady, they mark it as okay. It does seem like desiredNumberScheduled should also be checked though.

[nrb]

Does Octant do a similar check for Deployments? If so it might make sense to revisit our logic for declaring the Deployment ready; I'm still not convinced it's 100% accurate.

[prydonius]

@nrb yes, here's the one for deployments: https://github.com/vmware/octant/blob/f3702d9a64ba228b4ffa1c81b37be34780b1cf47/internal/modules/overview/objectstatus/deployment.go. There are other resource checks in that package