Prevent merge policies to be automatically deleted when one scoped member of the policy (host, network, storage, etc) is deleted or removed.

When creating merge policies, if for example, a cluster merge policy contains hostCluster1, hostCluster2 and hostCluster3, and one of those hostCluster is removed from vCenter or from Turbo, the merge police gets automatically deleted, so the customer don't know why the policy is now gone, as there is no notification in the UI and the customer is not able to re-use the policy for the other scoped resources.

This behaviour was tested by support, having a merge policy for Networks, they created NetGroup1, NetGroup2 and NetGroup3. When adding those groups to the merge policy and deleting any of those groups, the merge policy got automatically deleted with no visible notification on the UI. This behavior is also not documented under the merge policy documentation at:

https://www.ibm.com/docs/en/tarm/8.13.3?topic=policies-placement-policy-types#workload_placement_policy__merge_policy__title__1

The group deletion can be seen in the audit logs from within the rsyslog pod, but the automatic deletion of the merge policy is not on audit logs, but logged at the group component level within the rsyslog logs:

[turbo@node1 ~]$ kubectl logs rsyslog-7f5d766557-wvc4k | egrep MergeNet
group-6479dbd559-z5vjc: 2024-08-29 13:37:09,342  INFO [grpc-default-executor-190] [PolicyStore]    : Removing the following user-defined placement policies because of removal of groups [286737663892384] they are create on top of: [286737664862944(MergeNetTest1)]
group-6479dbd559-z5vjc: 2024-08-29 14:11:37,546  INFO [grpc-default-executor-193] [PolicyStore]    : Removing the following user-defined placement policies because of removal of groups [286737680236864] they are create on top of: [286737697646704(MergeNet2),286737698202752(MergeNet3)]