Enable CNI flexibility in a Kubernetes bundle installs

***Problem description
There is an issue that when a charmed k8s deployment is being deployed to juju, the CNI (when removed from the bundle) is still searched for by juju for about 30 minutes.

***Desired behavior
It would be desirable to somehow tell juju that a CNI will not be deployed (so that independent deploys of CNI can be made).