feat: publish superset helm chart

[jawabuu]

SUMMARY

This PR adds a simple chart releaser action to package and publish the superset helm chart.
A chart release will be created with the name superset-helm-chart-{{version}}
The chart repo will be available at https://apache.github.io/superset
A user will only need to run the following to install superset as opposed to cloning the entire repository.
helm repo add superset https://apache.github.io/superset
helm install superset/superset

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Clone the repo.

ADDITIONAL INFORMATION

• Has associated issue: Package helm chart #14037
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API
  @amitmiran137

[amitmiran137]

Thank you so much for your contribution!!

[craig-rueda]

Thanks, this is great!

[craig-rueda]

After taking a closer look, I think we need a few tweaks

[danielewood]

Has this been tested? I was going to be submitting a nearly identical PR. I ran into some issues when creating my action. Namely I needed to add the upstream chart repos to the released action. You can see what I did and copy that over if you want:
https://github.com/danielewood/charts/blob/f38d51ffc34e46fe0e58d561878fed3e1ac326b1/.github/workflows/release-charts.yaml#L24-L26

Also, is it the intent to publish a new chart on every PR merge? I would assume you only publish a new chart of you have modified the existing charts.

You can add:

paths:
    - 'helm/**'

To make this action trigger on only modifications to the charts.

[Hokwang]

waiting this

[jawabuu]

@craig-rueda Should be good now.
Lint is running on pull requests and will fail if chart changes were made but version was not incremented.
Release will package and create artifact only on push to master. Note that artifact creation will fail if there is an existing release with the same tag but this will already be caught by the linter.

[craig-rueda]

Can you also make a dummy change to something in the chart so we can see the linter working?

[jawabuu]

Can you also make a dummy change to something in the chart so we can see the linter working?

Done. However I don't think new tests in a PR are run, they need to be in master if I'm not wrong.

[craig-rueda]

Fair enough. Let's try it.

[jawabuu]

@craig-rueda on standby : )

[craig-rueda]

Looks like it failed: https://github.com/apache/superset/actions/runs/756228516

[jawabuu]

Yes it did. Seems you have policies on what actions can run in your repo. Let me check.

[craig-rueda]

I'll open a ticket with Apache Infra and see if I can get it allow-listed

[jawabuu]

Thank you!

[jawabuu]

@craig-rueda Once you do, we'll probably need to update the documentation to point users to https://apache.github.io/superset as the superset helm repo.