Updated common config file as part of SCT feature

[rajendraindukuri]

Description

• Updated common config file
• Excluded rule G101 to avoid false positive "Potential Hardcoded credentials"

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#876

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have maintained backward compatibility

How Has This Been Tested?

Tested using local csm operator runs and the results look good

When storageCapacity flag is set to false:

When storageCapacity flag is set to true:

[rajendraindukuri]

Gosec issue we are seeing here is a false positive and needs a human intervention to see if it is an actual issue. I checked the same and does not seem to be a potential security threat. So I am planning to exclude that particular issue.
PFB link for more details:
securego/gosec#295