CronJob chart new version - adds support for external secret using ClusterSecretStore

[yuvii]

Description

Creates new cronjob chart (1.6) which fixes the CronJob chart to support ClusterSecretStore in external secret template (aligns it with devtron app template configuration).

Edit:
Also fixed #6437 - changed restartPolicy to be a variable and not hard coded (similar to how the app is set up) ,

[gitguardian]

⚠️ GitGuardian has uncovered 2 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
2763127	Triggered	Generic High Entropy Secret	0a00d51	scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/secrets-test-values.yaml	View secret
141558	Triggered	Generic High Entropy Secret	0a00d51	scripts/devtron-reference-helm-charts/cronjob-chart_1-6-0/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.}

[sonarqubecloud]

Quality Gate passed

Issues
84 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[satyampsoni]

Hi @yuvii, thanks for the PR!Appreciate your contribution. We're currently considering deprecating this, so I'm putting the PR on hold for now.

[yuvii]

@satyampsoni what do you mean by deprecating "this"? Are you deprecating the entire CronJob chart and it won't be an option? Or are you merging it into the basic Deployment chart in some way?