fix: getting force_security_scan value from devtron-cm

[gireesh-naidu]

Description

Issue: we are fetching dashboard-cm to read a variable,but the name of the variable is not always same.this will cause error if the CM of dashboard is different(not devtron-cm).

Fix: now maintaining the variable in devtron-cm that is being fetched from dashboard-cm ,which will resolve the issue for now. later this variable will be removed from dashboard-cm and communicated to dashboard from orchestrator.
Fixes #3594

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

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?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication