[CPCAP-4657] - Feat: Release automation

[pranavcracker]

Summary

Adopts ci-tools' native GitHub↔GitLab release-automation pattern

Changes

Chart field-shape change (⚠️ breaking)

• image changed from an object (repository/pullPolicy/tag) to a combined string (image: repo:tag), imagePullPolicy promoted to a sibling key. Required because charts-values-update-action's version-bump does a plain-text repo:tag match and can't resolve a tag split across two keys.
• Updated: templates/deployment.yaml, values.schema.json, installation.md, ci/cloud-tests/cluster.yaml.

New workflow structure

• helm-charts-release.yaml rewritten workflow: check-tag → load-docker-build-components → docker-check-build → chart-release (bakes version, packages chart) → docker-build → github-release.
  • Added a publish_release input (default true) — github-release runs if: inputs.publish_release, so a manual test dispatch can explicitly opt out of creating a real GitHub Release by unchecking it.
  • Added chart-version computation — Chart.yaml needs valid SemVer, Docker tags don't, so test values like test-verify1 become 0.0.0-test-verify1 for the chart only.
  • New .qubership/helm-charts-release-config.yaml, .qubership/docker-build-config.cfg.
• publish.yaml → push.yml : every branch push now builds+publishes all 6 images tagged with the sanitized branch name, plus stale-version cleanup.
• build.yaml removed — fully subsumed by push.yml.

Breaking change ⚠️

Existing values.yaml overrides using image.repository/image.tag/image.pullPolicy need to migrate to image: <repo>:<tag> / imagePullPolicy: <policy>.