helm: disable arangolocalstorage crds when enableCRDManagement is false

[wyattwalter]

As a user of the operator, when I set operator.enableCRDManagement to false, I expected that the helm chart will not try to manage CRDs. However, if I set operator.features.storage to true, that enables CRD for that specific operator. This is causing conflicts for me because CRDs are defined cluster-wide, but I want to have the operator deployed into multiple namespaces.

This changes the behavior to only install the CRDs for the storage operator when both operator.features.storage is true and operator.enableCRDManagement is true.

I do not see a test suite for the Helm charts in this repo, but feel free to point me at one if there is. I checked it locally with:

$ helm template . --set operator.features.storage=true | grep arangolocalstorages.storage.arangodb.com
    name: arangolocalstorages.storage.arangodb.com
$ helm template . --set operator.enableCRDManagement=false --set operator.features.storage=true | grep arangolocalstorages.storage.arangodb.com