chore(workflow): bump charts automatically when controller is released

[simenandre]

This pull request adds a job in release-controller.yml which should automatically change appVersion in Charts.yml and image.tag in values.yaml (both located in charts/caddy-ingress-controller).

The idea behind this is as such: When developers make changes to the controller, we release a new version. However, we don't necessarily release new versions of our charts. This changes our flow to make it easier to roll out changes in charts easier. The flow typically will look like this if this is landed:

graph TD
    A[Create a new release/tag]
    B[Workflow triggered by tag event]

    A-->B

    C[Package controller with GoReleaser]
    D[Update Chart.yml and values.yml]
    E[Create pull request]

    B-->C
    B-->D
    D-->E

Note: We could even update version in Charts.yml with a patch version bump, triggering the workflow in release-chart.yml. Let me know if any of this would work out :)

[Embraser01]

Note: We could even update version in Charts.yml with a patch version bump, triggering the workflow in release-chart.yml. Let me know if any of this would work out :)

Good idea!

I'm good with the concept of automatically bumping the chart when a new controller version is released. We will still have to bump it manually when changing the chart which may cause some weird behavior like bumping the version twice between a release. I don't know if we can conditionally bump the version only if needed 🤔

[simenandre]

I'm good with the concept of automatically bumping the chart when a new controller version is released. We will still have to bump it manually when changing the chart which may cause some weird behavior like bumping the version twice between a release. I don't know if we can conditionally bump the version only if needed 🤔

We can use some magic like semantical commits to evaluate when to bump or not, not sure. Would it make sense to just have a pull request flow for now, and see how that all works out?

[Embraser01]

I'm good with the concept of automatically bumping the chart when a new controller version is released. We will still have to bump it manually when changing the chart which may cause some weird behavior like bumping the version twice between a release. I don't know if we can conditionally bump the version only if needed 🤔

We can use some magic like semantical commits to evaluate when to bump or not, not sure. Would it make sense to just have a pull request flow for now, and see how that all works out?

Let's go with that, and see alter if we can improve this. Thanks!