Fix OLM install modes

Currently with OLM we claim to support `OwnNamespace`, `SingleNamespace`,
and `AllNamespaces` install modes.

However, only `OwnNamespace` works properly when deploying OpsManager.
With other install modes, the operator is able to reconcile resources
and create `StatefulSets` for the workloads in OpsManager,
but pods never become healthy because only the operator's own namespace
has the required `ServiceAccount`.

With this change, we make the relevant `ServiceAccount`
managed by OLM. This means the `ServiceAccount` and relevant roles
will be created in all required namespaces.

Author: m1kola

Makefile

@@ -388,6 +388,7 @@ bundle: manifests kustomize
 	operator-sdk generate kustomize manifests -q
 	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)\
 		--channels=stable --default-channel=stable\
+		--extra-service-accounts mongodb-kubernetes-appdb \
 		--output-dir ./bundle/$(VERSION)/
 	operator-sdk bundle validate ./bundle/$(VERSION)