feat: propagate labels such as envName and projectName

[prakash100198]

Description

This pr addresses the issue that we don't export appName, envName and project into k8s objects managed in devtron.
Fixes #5031

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9257608	Triggered	Base64 AWS keys	dc23583	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/test-values.json	View secret
9257608	Triggered	Base64 AWS keys	8e61016	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/test-values.json	View secret
2763127	Triggered	Generic High Entropy Secret	8e61016	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/secrets-test-values.yaml	View secret
2763127	Triggered	Generic High Entropy Secret	dc23583	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/secrets-test-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	dc23583	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/env-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	8e61016	scripts/devtron-reference-helm-charts/deployment-chart_4-20-0-prakash-test1/env-values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud