Ensure configMapName Value is Used Consistently Across Templates

[Fovty]

Motivation

This change aims to address the issue where the configMapName key in the kube-downscaler Helm chart does not correctly set the name of the generated ConfigMap.

• Solves: The name of the ConfigMap for the kube-downscaler is not possible to control via the configMapName key in the Helm values.yaml file #55

Changes

• Updated templates/configmap.yaml to use the value of configMapName for the ConfigMap name.
• No changes to templates/deployment.yaml - already using the value of configMapName.

Tests done

• Rendered the Helm templates locally using helm template to verify that the configMapName value is correctly applied in the generated Kubernetes manifests.

TODO

• I've assigned myself to this PR

[github-actions]

File	Coverage
All files	97%	✅
test_autoscale_resource.py	99%	✅
test_cmd.py	100%	✅
test_events.py	100%	✅
test_grace_period.py	100%	✅
test_ignore_if_labels_dont_match.py	100%	✅
test_main.py	100%	✅
test_pods_force_uptime.py	100%	✅
test_resources.py	100%	✅
test_scaler.py	95%	✅
test_time.py	100%	✅

Minimum allowed coverage is 70%

Generated by 🐒 cobertura-action against 8042c33