Importing s3-operator chart as a helm chart dependency deploys CRDs after custom templates

Hi, I tried to use the s3-operator chart in order to manage resources on a MinIO instance outside of my cluster. However, when I import it as a dependency to my main chart, it is unable to install the chart due to some CRDs not being installed before Helm tries to install the custom templates (Bucket/Policy/S3User) I defined in my chart.

The value `crds.install` was indeed set to true, and if I remove the deployment of my templates the CRDs are installed.

Reading the advices from the [documentation of Helm](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#install-a-crd-declaration-before-using-the-resource), it seems like if the CRDs were placed in a `crds` folder inside the chart, Helm would be able to detect them and install them before everything else.