Elemental CAPI Publish a Helm chart

[anmazzotti]

Since the deployment of the Elemental operator is getting complex, we have a dependency on cert-manager, and we start having configuration variables and logic, it would be best to provide a Helm chart.

The Helm chart should be then the preferred way to deploy the operator.
The chart should also contain an Ingress template to optionally expose the Elemental API.

[anmazzotti]

Linking parent epic #968

[anmazzotti]

Closing this one as won't do.

The reason is that deploying the provider using Helm would differ from what other CAPI providers do.

Sticking to clusterctl is the best approach.

For Helm deployments, we can make use of the Rancher Turtles chart and let it include the Elemental provider by default.

Configuration variables can be provided by the user with a custom secret: https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/api/v1alpha2/provider_types.go#L52