[BUG]: CSM Operator not deleting the deployment and daemon sets after deleting the CSM

[riya-kaushal7997]

Description

After deleting the CSM the Operator not clearing the pods. When driver is deployed without forceRemoveDriver field in the CR, it sets forceRemoveDriver to false by default. Hence the driver pods still persists even after deleting CSM.

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1604

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.

The operator e2e tests were executed successfully. Full log attached in Jira ticket.

• Executed tests to install Powermax, Powerstore, Powerflex, Powerscale, and Unity (as Minimal, Standalone)
• Executed tests for Powermax, Powerstore, Powerflex, Powerscale and Unity with empty forceRemoveDriver (Minimal)
• Executed tests for Powermax, Powerstore, Powerflex, Powerscale and Unity with forceRemoveDriver set to false (Minimal)

[harishp8889]

Please update the PR description and add the appropriate e2e as per our discussion.