operator-framework-e2e: we should verify eventual consistency between catalog unpacking and operator resolution

[joelanford]

In the follow code, we create a Catalog and wait for it to be unpacked before we create the Operator:

operator-controller/test/operator-framework-e2e/operator_framework_test.go

Lines 334 to 337 in a00a93f

	By("creating a Catalog CR and verifying the creation of respective packages and bundle metadata")
	operatorCatalog, err = createCatalogCheckResources(operatorCatalog, catalogDInfo)
	Expect(err).ToNot(HaveOccurred())

We should change this (and similar) tests in all e2es such that Catalog and Operator creation/update happens roughly simultaneously or in random orders (e.g. create/update Operator before creating/updating a Catalog).

If we make this change, the expectation is that everything continues to work as is (modulo some timeout tweaks, perhaps) because we have ostensibly built an eventually consistent set of controllers.