Disable deployment of CRD tridentorchestrator in helm chart

[CodeGlitcher]

Describe the solution you'd like
Currently the helm char automatically deploys the tridentorchestrator crd in the same namespace as the operator.
In our cluster we currently have the tridentorchestrator and operator deployed in seperate namespace.
(we have all operators in the same namespace and the application they manage in a different 1.

We would like a option to deploy the tridentorchestrator in a different namespace,
or the option to not deploy the tridentorchestrator with helm but separately.

[CodeGlitcher]

We can try to create a pr to add this.
Is this a feature you want to add to the helm chart?

[woutersmit]

I have the same requirement (orchestrator in a different namespace) and have code ready for this in a fork.