HO bump to v0.1.48 fails due to new HO crashing 

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x37a4d7e]
goroutine 69 [running]:
github.com/openshift/hypershift/hypershift-operator/controllers/hostedcluster/metrics.(*hostedClustersMetricsCollector).Collect(0xc000e3cbc0, 0xc0007082a0)
    /hypershift/hypershift-operator/controllers/hostedcluster/metrics/metrics.go:476 +0x2cfe
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
    /hypershift/vendor/github.com/prometheus/client_golang/prometheus/registry.go:455 +0x189
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather in goroutine 181
    /hypershift/vendor/github.com/prometheus/client_golang/prometheus/registry.go:547 +0xddd

    4.18

100%    

    1. Bump HO from v0.1.47 to v0.1.48
    2.
    3.
    

    fails to use new HO version

    Sucessfully uses new HO version

    this is caused because the etcdRecoveryActive status is only present when the job is trigerred and we dont nil check it during metric collection