feat: move lint test chart to seperate action and trigger it on reg tests

[kostasrim]

• move lint test chart to a separate action
• use it in regression tests

[kostasrim]

reg-tests run: https://github.com/dragonflydb/dragonfly/actions/runs/7775721351/job/21202001341

[romange]

@Pothulapati what this step does? does it change release the new version of helm templates?

[Pothulapati]

@romange This test just runs the Helm Charts against a kubernetes cluster to make sure things work (using https://github.com/helm/chart-testing). I don't think this workflow releases a new file.

Currently, Its failing on the Password Var deprecation and #2539 fixes that.

[romange]

Do you guys understand why some steps have if: github.event_name == 'workflow_dispatch' condition @kostasrim @Pothulapati ?

[Pothulapati]

@romange Not exactly sure why they exist but my guess would be that as they involve running a Kubernetes cluster they thought it was not necessary to run them per PR and only when they want but for runtime bugs (like the password one), It's the only way to find them is to run them.

Considering that this new regression job runs on a schedule and on a trigger, I guess it makes sense to remove the toggle entirely and have this run everytime. wdyt?

[romange]

I agree, @kostasrim ^^

[kostasrim]

I kept this because if the job gets triggered manually it will become true. I am not sure about the && -all` part, I am running the reg tests manually to see how it affects it and I will remove it if it's not used.

[kostasrim]

yep we need it. see https://github.com/helm/chart-testing/blob/main/doc/ct_lint.md and --all