Description of problem:

When a ConfigurationPolicy stops managing an object, it is always deleted regardless of pruneObjectBehavior being set to `None`.

Below are a few examples of when a ConfigurationPolicy would stop managing an object:

• The ConfigurationPolicy is updated to manage a different object.
• The ConfigurationPolicy's namespaceSelector is changed.
• The ConfigurationPolicy's templating resolves differently based on changing conditions to no longer manage an object.

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

How reproducible:

Very reproducable

Steps to Reproduce:

1. Create a ConfigurationPolicy with pruneObjectBehavior set to "None" (default) that creates/updates a ConfigMap called "test"
2. Update the ConfigurationPolicy to create/update a ConfigMap called "not test"

Actual results:

After following the reproducing steps, the ConfigMap called "test" is deleted.

Expected results:

After following the reproducing steps, the ConfigMap called "test" should not be deleted.

Additional info:

This will cause unexpected data loss to customers.