User Story:
As an OpenShift Engineer I want modify the existing csi operator project jobs to disable storage during install and then re-enable afterwards so that we can start testing the behavior of the CCM changes before the upstream changes are pulled in.

Description:
Currently we are waiting on several upstream changes to be completed before we can continue development on the storage portion of the vSphere hybrid environment feature.  The two features we need are:

• CCM vSphere to support adding custom labels to nodes
• kubernetes test config object allows setting additional label selector for storage tests

The intent here is to update the CSI operator jobs for hybrid to configure install config to disable storage operator and then re-enable it after install.  In theory, we can also just leave it off like in the other tests; however, since this is the storage tests, re-enabling is a must.

Acceptance Criteria:
The hybrid install passes; but fails during e2e which is expected until the storage tests can be allocated to only vsphere nodes.

Other Information:

issue created by splat-bot