Description of problem:

When disabling edge-manager, the "flightctl-db-migration" pod remains as well as the PVC "flightctl-alertmanager-data-flightctl-alertmanager-0". If you then enable edge-manager again, it will create a new DB migration pod and will keep doing so every time you enable and disable the component.

Similarly, the following resources also do not get cleaned up when the component is disabled:
ClusterRole: flightctl-client
ClusterRoleBinding: flightctl-agent-registration, flightctl-client

Version-Release number of selected component (if applicable):

"acm_image": "quay.io:443/acm-d/acm-dev-catalog:2.15.0-DOWNSTREAM-2025-10-08-15-13-27",
"mce_image": "quay.io:443/acm-d/mce-dev-catalog:2.10.0-DOWNSTREAM-2025-10-09-01-16-59",

How reproducible:

Always

Steps to Reproduce:

1. Install the build above.
2. Toggle edge-manager-preview a few times.

Actual results:

The pod and PVC should be deleted upon disabling of the component.

Expected results:

The pod gets created repeatedly and the PVC remains.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 11/3/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.

Additional resources were listed in a dedicated "removal" section of the operator code. 

Key Areas to Verify:

1. the migration pod and the PVC should be gone now
2. The secrets should also be gone
3. The ClusterRole and ClusterRoleBindings should also be gone

Fix or Feature Availability:
When will this be available in a build? Right now
Expected downstream build tag (if known): latest-2.15