fix(orchestrator): use versioned name for the DB creation Job to avoid immutable upgrade errors (#427)

The `<release>-create-sonataflow-database` Job uses a fixed name across
chart versions. When a field in the rendered pod spec changes between
versions (e.g. the pinned PostgreSQL image digest), an in-place
`helm upgrade` of an Orchestrator-enabled release tries to patch the
Job's immutable `spec.template` and fails:

  Job.batch "<release>-create-sonataflow-database" is invalid:
  spec.template: ... field is immutable

Use a versioned name `<release>-create-sf-db-<chart-version>` so each
chart version gets a distinct Job (recreated instead of patched).

This is the minimal part of #407 needed to fix the upgrade; the
fail-hard / configurable backoffLimit changes (RHDHBUGS-2577) are
intentionally left out of the 1.10 line.

Fixes RHDHBUGS-3325. Targets 1.10.1.

Signed-off-by: Gustavo Lira <guga.java@gmail.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: gustavolira

charts/backstage/templates/sonataflows.yaml

@@ -85,7 +85,7 @@ spec:
 apiVersion: batch/v1
 kind: Job
 metadata:
-  name: {{ .Release.Name }}-create-sonataflow-database
+  name: {{ .Release.Name }}-create-sf-db-{{ .Chart.Version | replace "." "-" }}
   namespace: {{ .Release.Namespace }}
 spec:
   activeDeadlineSeconds: 120