adding support for workload identity in neo4j admin backup

[renetapopova]

No description provided.

[neo-technology-commit-status-publisher]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

[harshitsinghvi22]

For example , a service account with workload identity if you want to use workload identity integration to access the cloud provider bucket.

You can use the above line instead of if processes....

[renetapopova]

But it doesn't say why it is desirable... How about something like this:
"In certain situations, it may be useful to assign a Kubernetes Service Account with workload identity integration to the Neo4j backup pod. This is particularly relevant when you want to improve security and have more precise access control for the pod. Doing so ensures that secure access to resources is granted based on the pod's identity within the cloud ecosystem."

[harshitsinghvi22]

serviceAccountName field is not part of neo4j ..and keep secretNAme and secretKeyName empty for serviceAccount with workload identity examples

neo4j:
  image: "neo4j/helm-charts-backup"
  imageTag: "5.13.0"
  jobSchedule: "* * * * *"
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1
  backoffLimit: 3
backup:
  bucketName: "my-bucket"
  databaseAdminServiceName:  "standalone-admin" #This is the Neo4j Admin Service name.
  database: "neo4j,system"
  cloudProvider: "gcp"
  secretName: ""
  secretKeyName: ""
consistencyCheck:
  enabled: true
serviceAccountName: "demo-service-account"