update release action to auto release kustomize yaml's as assets

[Links2004]

this change will add kustomize yamls to the release as assets and create a draft release.
by doing this it is possible to simply use:

resources:
- https://github.com/Links2004/grafana-operator/releases/download/t5.0.9/kustomize-cluster_scoped.yaml
or
- https://github.com/Links2004/grafana-operator/releases/latest/download/kustomize-cluster_scoped.yaml

this will not need any OCI support and allow easy usage with kustomize or kubectl.

see: #1367

example run: https://github.com/Links2004/grafana-operator/actions/runs/7408779579/job/20157697759
example release: https://github.com/Links2004/grafana-operator/releases/tag/t5.0.9

[Links2004]

feel free to add the release text generator you use so get the correct message directly in the draft, did not find the reference what is used in the repo.

[NissesSenap]

Thanks @Links2004 for taking a stab at this.
Added a few comments.
It would be nice to include the CRDs as a separate bundle. This, since helm can't handle CRD updates through helm install.
But I can handle that part if you don't feel like it.

It would also be nice to add some basic documentation about how to use the new Kustomize artifacts to install it to a cluster.

[Links2004]

Added some docu, links are manually created and work(TM) with the next release.

[NissesSenap]

Thanks for the quick update, I added a minor comment, I will try to get time to verify the release processes later today.

[NissesSenap]

I personally use server side apply instead of replace.

metadata:
  annotations:
    argocd.argoproj.io/sync-options: ServerSideApply=true

This way the kubectl.kubernetes.io/last-applied-configuration isn't created and the CRD don't get too big.
But I guess this is individual, maybe we should provide both suggestions?

[NissesSenap]

I added it on my own

[NissesSenap]

It seems to be working as expected. It might be some issue with packages: write as well. But lets see how it goes.
Thanks allot @Links2004