With csi operator enabled dont create rook-ceph-csi-config cm

Is this a bug report or feature request?

Deviation from expected behavior:

With csi operator enabled dont create rook-ceph-csi-config cm
As the CSI will manged by csi oeprator in that case

And also clean any cm if its present with the upgrades and we switched to use csi operator

Expected behavior:

rook-ceph-csi-config cm should not be created with csi operator

How to reproduce it (minimal and precise):

File(s) to submit:

Logs to submit:

Operator's logs, if necessary
Crashing pod(s) logs, if necessary

To get logs, use kubectl -n <namespace> logs <pod name>
When pasting logs, always surround them with backticks or use the insert code button from the Github UI.
Read GitHub documentation if you need help.

Cluster Status to submit:

Output of kubectl commands, if necessary

To get the health of the cluster, use kubectl rook-ceph health
To get the status of the cluster, use kubectl rook-ceph ceph status
For more details, see the Rook kubectl Plugin

Environment:

OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Cloud provider or hardware configuration:
Rook version (use rook version inside of a Rook Pod):
Storage backend version (e.g. for ceph do ceph -v):
Kubernetes version (use kubectl version):
Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift):
Storage backend status (e.g. for Ceph use ceph health in the Rook Ceph toolbox):

Provide feedback