Validate follower pod owned by same Job as leader pod

[danielvegamyhre]

This change validates the leader pod has same owner UID as the follower, to ensure they are part of the same Job.
This is necessary to handle a potential race condition between index updates and pod rescheduling during JobSet restarts.

1. A job failure occurs and the JobSet is restarted (deleting and recreating all jobs)
2. Leader pods may land on different node pools than they were originally scheduled on.
3. When the follower pods are recreated, and we look up the leader pod using the index which maps
   [pod name without random suffix] -> corev1.Pod object, if this occurs before the index updates for the leader pod have been pushed to the controller, we may get a stale index entry and inject the the wrong nodeSelector, using the topology the leader pod was originally scheduled on before the
   restart.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielvegamyhre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [danielvegamyhre]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-jobset canceled.

Name	Link
🔨 Latest commit	4f5afd3
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-jobset/deploys/65de8a8c67c58a0008ba4169

[kannon92]

I am going to leave LGTM for @ahg-g on this one. I don't really have much context into this problem.

[ahg-g]

/lgtm