feat: Manually chown in the case when fsGroup not respected

[as51340]

Some storage classes don't support fsGroup. In that case, user should manually chown on the volumes used. This feature allows easier chown by just setting a switch. Inspired by mysql-operator.

[as51340]

Tracking

• [Link to Epic/Issue]

Standard development

• Update / add chart templates, values, and NOTES.txt as needed
• Run helm lint and helm template locally against the changed chart(s)
• Verify the chart installs and upgrades cleanly on a test cluster

Labels checklist

• Add a docs label (exactly one): docs-changelog-only, docs-needed, or docs-not-needed
• Add at least one component label: memgraph, memgraph-ha, memgraph-lab, or infrastructure
• Add at least one type label: bug, feature, or infrastructure
• Assign the PR to a milestone
  • If not known, set for a later milestone

Documentation checklist

• Write a release note, including added/changed clauses
  An init container can now be added by enabling fixOwnershipInitContainer value which will chown to memgraphUserId:memgraphGroupId in situations when used storage class doesn't support fsGroup. #243
  • What has changed? What does it mean for a user? What should a user do with it? [#{{PR_number}}]({{link to the PR}})
• Documentation PR link
  • Is back linked to this development PR

[mattkjames7]

I think we should specify a version for busybox, but otherwise looks good