✨ Publish helm charts on each operator release

[alexander-demicev]

What this PR does / why we need it:

First of all, this PR introduces a release workflow similar to what is done in CAPI, which will be triggered on a new release tag push. This workflow will create a draft release and publish a helm chart.
I didn't find any best practices on managing helm repositories in kubernetes-sigs so we will host our repository using github pages and publish helm charts using helm/chart-releaser-action action.

I created a new set of kustomize configurations so we can manage manifests for helm charts separately because they have to be handled in a slightly different way and this will allow us to modify them later independently.

This repository will also be used as a helm chart repository, we will host index.yaml in root of project and update it with every release, I will create release docs in the next PR.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[Fedosin]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Fedosin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Fedosin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment