Describe the problem

In #59760 we introduce a job to run cluster version migrations. This is great because it offers many benefits of the jobs ecosystem like pausing and mutual exclusion. A downside is that a full cluster backup is going to pick up those jobs which may not be safe to resume on the restored cluster.

Possible Solution

I'm thinking a simple solution would be to encode the cluster id of the creating cluster into the job. Then, when the job is resumed on a different cluster, it can just error out.

Epic CRDB-8816

Jira issue: CRDB-3191