fix(helm): rename jobs to their used helm command

This should avoid confusion by helm users:

- `.helm:build` became `.helm:package`
- `.helm:push` became `.helm:cm-push`

templates/Helm.yaml

@@ -5,9 +5,9 @@
 #
 # - `.helm:lint`: verify formatting of the helm chart
 #
-# - `.helm:build`: build the helm package tgz file
+# - `.helm:package`: build the helm package tgz file
 #
-# - `.helm:push`: push the helm package tgz file to a remote
+# - `.helm:cm-push`: push the helm package tgz file to a remote
 #   repository
 #
 ---
@@ -64,8 +64,8 @@
 
 
 #
-# .helm:build
-# ===========
+# .helm:package
+# =============
 #
 # Build the helm package tgz file
 #
@@ -80,7 +80,7 @@
 # stages:
 #   - build
 #
-# helm build: {extends: '.helm:build'}
+# helm build: {extends: '.helm:package'}
 #
 # REQUIREMENTS
 # ============
@@ -107,7 +107,7 @@
 # USED CI VARIABLES
 # =================
 #
-.helm:build:
+.helm:package:
   stage: build
   extends:
     - .helm:base
@@ -122,10 +122,10 @@
 
 
 #
-# .helm:push
-# ==========
+# .helm:cm-push
+# =============
 #
-# Push the helm package tgz file to a remote repository
+# Push the helm package tgz file to a remote chartMuseum repository
 #
 # USAGE
 # =====
@@ -138,7 +138,7 @@
 # stages:
 #   - release
 #
-# helm publish: {extends: '.helm:push'}
+# helm publish: {extends: '.helm:cm-push'}
 #
 # REQUIREMENTS
 # ============
@@ -146,7 +146,7 @@
 # - a `release` stage must be present in your pipeline or it must be
 #   overriden by the extending job to feet your need.
 #
-# - the `.not-on-stable` rules templates or it must be overriden by
+# - the `.on-release-tag` rules templates or it must be overriden by
 #   the extending job to feet your need
 #
 # - `HELM_REPO` variable: URL of the helm ChartMuseum
@@ -172,7 +172,7 @@
 # USED CI VARIABLES
 # =================
 #
-.helm:push:
+.helm:cm-push:
   stage: release
   extends:
     - .helm:base