As a mesh admin, I want the OSSM operator to delete the istio-cni-node DaemonSet when the last SMCP is deleted so that my cluster doesn't run Pods that I no longer need.

The operator starts up the istio-cni-node DaemonSet the first time you deploy an SMCP. It never deletes this DaemonSet. It's fairly easy to implement the deletion of this DaemonSet when the last SMCP is deleted.

Also important is the fact that we now create different a DaemonSet based on the version in the SMCP. If someone creates a v2.2 SMCP, the istio-cni-node DaemonSet is created. If they then upgrade the SMCP to v2.3, the istio-cni-node-2-3 DaemonSet is created alongside the first DaemonSet. The first DaemonSet is no longer used, so it should be deleted.

Acceptance criteria:

• When you create an SMCP in an empty cluster and then delete it, the DaemonSet is deleted.
• When you create multiple SMCPs and then delete one, the DaemonSet should NOT be deleted.
• When you deploy multiple SMCPs with different versions and then delete the SMCPs of a particular version, only that version's DaemonSet is deleted.
• When you create a v2.2 SMCP and then upgrade it to v2.3, only the 2.3 DaemonSet remains.
• Create OSSMDOC ticket explaining the new functionality.