Consider adding a changelog or useful notes to Github releases

**Is your feature request related to a problem?**

This is not really a feature request for the helm charts, but the repo itself. When operating a cluster, we have to check changelogs of all the applications we are running to ensure there are no breaking changes or changes that would affect how we operate the application.

We are now also using [Renovate](https://github.com/renovatebot/renovate) to automate helm upgrades (via PRs) to our Pulumi managed EKS clusters and this repo does not include either a CHANGELOG.md file anywhere and the Github releases do not include any useful information about what was actually released. Adding either of these will ease the burden of checking all commits between versions.

**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
[aws-load-balancer-controller](https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller) is the main pain point for us right now.

**Describe the solution you'd like**
Generation of a changelog file for each chart or a release for each chart version bump so that humans can discover what has changed more easily and automated tools like Renovate can read them and populate PRs.

**Describe alternatives you've considered**
Going through the commits between version bumps on the helm chart I am concerned with. A very tedious process. If there is another way, I am all ears.

Start with the stable/aws-load-balancer-controller chart and review how chart version bumps and GitHub releases are currently handled. Compare the requested per-chart CHANGELOG.md or release notes approach with what automated tools such as Renovate can consume; done means users can discover meaningful changes for each chart version.

Written by the indexing model from the issue text.