[Bugfix]: Powerflex minimal manifest issue

[mgandharva]

Description

Added validation for common and image for Powerflex minimal manifest

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1671

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
• I have executed the relevant end-to-end test scenarios

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Ran E2E for powerflex
• 

[prablr79]

@mgandharva update all details here, missing defect and checklist.

[bpjain2004]

Is this really required?

[JacobGros]

yes, because with minimal sample files, the replicas can be 0 in the CR. In this case, we want to use the default values in operatorconfig.

Without that check, the minimal manifests would deploy the driver pods w/o the deployment pods