Argo Rollout stores status.observedGeneration as a string, unlike the
int64 convention kstatus expects. Helm v4's status wait runs
status.Compute for CRDs, which errors on the string value; the error is
attached to the ResourceStatus as "Unknown" instead of being surfaced,
so the Rollout stays Unknown forever and --wait times out with
"waiting for resource ... kind=Rollout ... actualStatus=Unknown".
Treat a resource whose status could not be computed (Unknown with an
attached error) as ready when waiting for Current, matching Helm 3's
behavior of considering kinds Helm cannot evaluate as ready. Also prime
the RESTMapper before starting the status watcher's informers so a CRD
that is still being established does not cause an informer to be
permanently abandoned.
Signed-off-by: MrJack <36191829+biagiopietro@users.noreply.github.com>