feat(helm): add namespace override capability for multi-namespace deployments

[bwdmr]

Adds a new helper template "altinity-clickhouse-operator.namespace" that allows overriding the release namespace via Values.namespaceOverride. Updates all resource templates to use this helper instead of directly referencing .Release.Namespace. This change enables multi-namespace deployments in combined charts while maintaining backward compatibility.

Thanks for taking the time to contribute to clickhouse-operator!

Please, read carefully instructions on how to make a Pull Request.

This will help a lot for maintainers to adopt your Pull Request.

Important items to consider before making a Pull Request

Please check items PR complies to:

• All commits in the PR are squashed. More info
• The PR is made into dedicated next-release branch, not into master branch¹. More info
• The PR is signed. More info

--

¹ If you feel your PR does not affect any Go-code or any testable functionality (for example, PR contains docs only or supplementary materials), PR can be made into master branch, but it has to be confirmed by project's maintainer.

[Slach]

look to dev/generate_helm_chart.sh

all templates/generated shall be changed from this script

[Slach]

Sorry for disturbing you again

Could you clarify?
What is the goal for these changes?

Do you want to install helm chart to some namespace but install rendered manifest to another namespace?
Why?

Which behavior you try to achieve?

If you want to change operator watched namespace for example and install operator in one namespace but watch custom resources in another namespaces

just change values.yaml

  files:
    config.yaml:
      # empty value will watch all namespaces
      namespaces: [""]