Fix integration test setup

[carolynvs]

The integration tests has a hack right now where I deploy to the cluster, and then remove the controller so that the controller that is run by ginkgo doesn't collide with the deployed one and they both trigger when CRDs change. The deploy to the cluster is needed so that the CRDs are defined.

We should clean this up to not be such a hack (if for no other reason than it's slow). Some options are

• use EnvTest instead of pointing ginkgo at an existing cluster
• make a new kind cluster and only deploy the CRDs to it, leaving the dev cluster alone
• have the operator only respond to events in a specified set of namespaces, ignoring ginkgo, so that we can just reuse the dev cluster