time-series-analytics: Add "helm" suffix to helm charts (open-edge-platform#1814)

Updates the time-series-analytics Helm chart versioning scheme to add a -helm suffix,
aligning chart metadata and user documentation with the new published chart version format.

Signed-off-by: B, Vinod K <vinod.k.b@intel.com>

Author: vkb1

microservices/time-series-analytics/docs/user-guide/get-started/deploy-with-helm.md

@@ -23,14 +23,14 @@
 
     1. Download helm chart with the following command
 
-        `helm pull oci://registry-1.docker.io/intel/time-series-analytics-microservice --version 2026.0.0-<date>-weekly`
+        `helm pull oci://registry-1.docker.io/intel/time-series-analytics-microservice --version 2026.0.0-<date>-weekly-helm`
 
         Replace `<date>` with the actual patch version date (e.g., `20260120` for January 20th, 2026).
-        `helm pull oci://registry-1.docker.io/intel/time-series-analytics-microservice --version 2026.0.0-20260120-weekly`
+        `helm pull oci://registry-1.docker.io/intel/time-series-analytics-microservice --version 2026.0.0-20260120-weekly-helm`
 
     2. unzip the package using the following command
 
-        `tar -xvzf time-series-analytics-microservice-2026.0.0-<date>-weekly.tgz`
+        `tar -xvzf time-series-analytics-microservice-2026.0.0-<date>-weekly-helm.tgz`
 
     - Get into the helm directory
 

microservices/time-series-analytics/helm/Chart.yaml

@@ -23,15 +23,14 @@ type: application
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
 #
 # Before pushing helm charts to a chart repository:
-# 1. Update this version to format: 2026.0.0-<date>-weekly where <date> is in yyyymmdd format
+# 1. Update this version to format: 2026.0.0-<date>-weekly-helm where <date> is in yyyymmdd format
 # 2. Update the appVersion below with the same date
 # 3. Update the date in values.yaml file under images.weekly_build_date: "<date>"
 #
 # Example: If the release date is February 2, 2026:
-#   version: 2026.0.0-20260202-weekly
-#   appVersion: "2026.0.0-20260202-weekly"
+#   version: 2026.0.0-20260202-weekly-helm
 #   values.yaml -> images.weekly_build_date: "20260202"
-version: 2026.0.0
+version: 2026.0.0-helm
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
@@ -40,8 +39,8 @@ version: 2026.0.0
 #
 # Before pushing helm charts to a chart repository:
 # 1. Update this appVersion to match the chart version above (same date format)
-# 2. Ensure this matches the version field above: 2026.0.0-<date>-weekly
+# 2. Ensure this matches the version field above: 2026.0.0-<date>-weekly-helm
 #
 # Example: If the release date is February 2, 2026:
-#   appVersion: "2026.0.0-20260202-weekly"
-appVersion: "2026.0.0"
+#   appVersion: "2026.0.0-20260202-weekly-helm"
+appVersion: "2026.0.0-helm"