ci: add dev helm chart publishing workflow

[akashsinghal]

Description

What this PR does / why we need it:

• Removes all dev image publishing from release publish workflow (less chance for erroneous errors)
• Introduces dedicated dev-assets-publishing workflow to build CRD + Ratify + plugin + chart publishing
  • triggered every week Sunday morning 08:30 UTC
  • publishes dev helm chart with rolling tag 0-dev and 0-dev.<YYYYMMDD>.<7-character-commit-hash>. dev chart points to updated CRD + plugins dev image (Note 0- must be prepended for semver compatibility with helm)
  • publishes ratify CRD + ratify base + ratify plugins image. Each tagged with 0-dev.<YYYYMMDD>.<7-character-commit-hash> AND rolling tag latest
• updates dev.helmfile.yaml & dev.highavailability.yaml to point to rolling tag chart 0-dev and removes other previous manual value overrides
• updates dev.highavailability.yaml to install gatekeeper and constraint + constraint template. No longer any dependency on dev.helmfile.yaml.
• updates docs on how to use dev.helmfile.yaml and new streamlined release guidance.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• Does the affected code have corresponding tests?
• Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have appropriate license header?

Post Merge Requirements

• MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c2c51b6) 61.43% compared to head (7389568) 61.43%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1209   +/-   ##
=======================================
  Coverage   61.43%   61.43%           
=======================================
  Files          97       97           
  Lines        6179     6179           
=======================================
  Hits         3796     3796           
  Misses       2051     2051           
  Partials      332      332           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[junczhu]

LGTM

[susanshi]

LGTM. thanks!

[susanshi]

LGTM. thanks