Consider Revision in job names

In Helm, each release increments the revision number. We use this revision number in the name of some of our jobs:

• shared-secrets
• migrations

In testing the Operator, we noticed that in some situations updating the CR would trigger a new release, which attempted to create a new migrations job. However, because we don't have incrementing Revision numbers from the Helm template in the Operator, the Job name still uses 1 in the name for the revision, which causes an error in the Operator logs related to immutable fields.

We should look into a way to consider revision number so these jobs can be deployed correctly.