feat(metrics-operator): introduce v1 API version (#3266)

Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <93584209+odubajDT@users.noreply.github.com>

.sonarcloud.properties

@@ -15,6 +15,7 @@ sonar.cpd.exclusions= **/*_test.go,\
   metrics-operator/api/v1alpha2/**/*.go,\
   metrics-operator/api/v1alpha3/**/*.go,\
   metrics-operator/api/v1beta1/**/*.go,\
+  metrics-operator/api/v1/**/*.go,\
   **/zz_generated.deepcopy.go,\
   **/fake/**/*.go
 sonar.go.exclusions=**/vendor/**,\

README.md

@@ -52,7 +52,7 @@ Status of the different features:
 
 - ![status](https://img.shields.io/badge/status-stable-brightgreen)
   Observability: expose [OTel](https://opentelemetry.io/) metrics and traces of your deployment.
-- ![status](https://img.shields.io/badge/status-beta-yellow)
+- ![status](https://img.shields.io/badge/status-stable-brightgreen)
   K8s Custom Metrics: expose your Observability platform via the [Custom Metric API](https://github.com/kubernetes/design-proposals-archive/blob/main/instrumentation/custom-metrics-api.md).
 - ![status](https://img.shields.io/badge/status-beta-yellow)
   Release lifecycle: handle pre- and post-checks of your Application deployment.

chart/Chart.yaml

@@ -42,7 +42,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.5.1
+version: 0.5.2
 # 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
 # follow Semantic Versioning. They should reflect the version the application is using.