Proper release process

[bo0tzz]

Currently the chart is built and released whenever a new chartVersion is pushed to main. Depending on the options out there, it would be nice to make this a bit more deliberate to increase the control over when new versions are published.

Currently releases do not include any changelogs. This should be fixed so that both the github releases and the artifacthub page properly display a changelog, and ideally so that these changelogs also show up in PRs generated by tools like Renovate.

[hiteshnayak305]

i will try change log generators for CHANGELOG.md and artifacthub annotations. for now we need to update contribution guide to use conventional commit messages.

[kriegalex]

The default chart also fails to pass a proper CD/CI pipeline using the default values, because existingClaim is mandatory.

In the case of Github Actions, you can easily spawn a KIND cluster to test a helm chart, but I'm not sure if it is easy to create a PVC in the github actions workflow. Even if it is possible, in my opinion, it should work with the default values out of the box, meaning it should create a default pvc when no existingClaim is provided. Maybe I'm wrong.

This would qualify as proper release process, as now you can accept more easily changes from outsiders knowing that the default values at least still work.