Refactor Job names to not rely on .Release.Revision

Split from #695 (closed)

In continued effort to allow for the use of these charts without the reliance on Tiller, @matthias.vandemeent found that many of our in-chart Job names rely on the use of .Release.Revision. This is problematic to the use case of helm template | kubectl apply because these will always be name: RELEASE-NAME-xxx.0, as template has no idea of the revisions.

We should look into a replacement for this behavior that is more resilient to all use cases, and does not rely specifically upon state data within Tiller to name these objects.

The following templates are not template-proof due to their reliance on .Release.Revision:

• minio.createBucketsJobName (overridable)
• migrations.jobname
• shared-secrets.jobname
• certmanager-issuer.jobname

We could consider two options:

1. Allow providing .Values.global.helmOverrides.Release.Revision
2. Replace .Release.Revision with a timestamp or other condensed identifier.