As a developer I want to make sure the Hypershift hosted cluster upgrades induce karpenter drift and the RHCOS version and Kubernetes version of the node match the versions of the release payload that we were upgrading the hosted cluster to. I also want to make sure the workloads on the old node are moved onto the new node.

We've figured out that karpenter drift with hypershift cluster upgrades works already as part of AUTOSCALE-1, now we have to e2e ci test it.

Since this is a feature that tests node upgrades inside a guest cluster, we can only test it from the hypershift side. We would probably stick the test here: https://github.com/openshift/hypershift/blob/main/test/e2e/karpenter_test.go

We need to create a hypershift e2e test (or if possible, integrate it into the existing test) that follows some flow like this: 
  * creates a hosted cluster that points to n-1 release version (by e2eutil.NewHypershiftTest)
  * creates and scales a workload that starts a karpenter node and schedules the workload
      * take note of the kubernetes version and the rhcos version of the node
  * upgrades the hosted cluster release image to version n
  * wait until the new nodeclaim and node are created and schedulable
      * make sure the k8s versions and rhcos version match the expected version of release image n
      * wait until the previous workload is scheduled to the new node, fail if it doesn't within a timeout