Fix Neo4j backup/restore runAsUser and Neo4j RestoreSession shape

[ArnobKumarSaha]

Neo4j BackupConfiguration

runAsUser was 999 in both security contexts built by the neo4j editor; Neo4j runs as 7474.

RestoreSession runAsUser

The uid lived in a 9-entry map in corekubestashcom-restoresession-editor-options/ui/functions.js,
which was out of sync with the real per-DB defaults in each kubedbcom-<db>-editor-options
container.securityContext helper. For any kind missing from that map — Neo4j, Cassandra, Kafka,
Solr, ClickHouse, DB2, … — spec.addon.jobTemplate.securityContext stayed empty and the whole
jobTemplate + containerRuntimeSettings block was dropped from the rendered RestoreSession.

The default now comes from a chart helper mirroring those 29 charts; the JS only supplies the
OpenShift sa.scc.uid-range override. RabbitMQ is intentionally absent — its options chart has no
container.securityContext helper, so it keeps today's behaviour.

One correction this brings along: ZooKeeper 999 → 1000, matching its options chart. Postgres stays
at 70 as before, even though kubedbcom-postgres-editor-options/templates/_helpers.tpl defaults to
999 outside timescaledb-* and old N.M versions.

Neo4j RestoreSession shape

For kind: Neo4j the restore job now also gets the target's data PVC and the seed pod parameter,
both derived from spec.target.name:

  addon:
    name: neo4j-addon
    tasks:
      - name: logical-backup-restore
        params: {seedServerName: "restored-neo4j-0"}
    jobTemplate:
      spec:
        volumes:
          - name: data
            persistentVolumeClaim:
              claimName: data-restored-neo4j-0
        volumeMounts:
          - mountPath: /data
            name: data
            subPath: data
        nodeSelector:
          kubernetes.io/os: linux
        securityContext:
          runAsUser: 7474
          runAsGroup: 0

setNeo4jParams() fills the parameter in on initMetadata and on target-name change; it stays
editable in the "Additional Parameters" textarea.

Verified

helm template of corekubestashcom-restoresession-editor-options:

• kind=Neo4j → volume/mount, runAsUser: 7474, params as a YAML flow map
• kind=MongoDB → 999, no volumes
• explicit spec.addon.jobTemplate.securityContext still wins
• kind=RabbitMQ and empty target → no jobTemplate block, as before

go build ./... and helm lint clean.