operator-sdk cleanup: remove packagemanifests, add generic command

[joelanford]

Description of the change:

• Removes operator-sdk cleanup packagemanifests <packageManifestsDir>
• Adds operator-sdk cleanup <packageName>
• Updates operator-sdk run packagemanifests to include owner reference on catalog source resources

Motivation for the change:
Simplify cleanup command to work with arbitrary installation methods (e.g. run packagemanifests and the upcoming run bundle)

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[joelanford]

There's some related work going on with run bundle in the github.com/operator-framework/operator-sdk/internal/operator package.

The thought is to do the new run design in the new package, and once that's mostly there we can port the existing run packagemanifests code (mainly the registry setup) into that package.

See #3626

[estroz]

Structurally looks fine, mostly nits/fixes.

[estroz]

Follow-up: helm's e2e tests should be using the test namespace, and run/cleanup should have --namespace=<tc.Kubectl.Namespace> in their command args.

[camilamacedo86]

Replace:

func TestE2E(t *testing.T) {
	RegisterFailHandler(Fail)
	RunSpecs(t, "Operator SDK e2e suite")
}

With:

// TestE2EGo ensures the Helm projects built with the Go tool by using its binary.
func TestE2EGo(t *testing.T) {
	if testing.Short() {
		t.Skip("skipping Operator SDK E2E Go Suite testing in short mode")
	}
	RegisterFailHandler(Fail)
	RunSpecs(t, "E2EGo Suite")
}

Otherwise, the test will be called in the target make test-unit

[estroz]

make test-unit skips the entire test package with go list ./... | grep -v -E 'github.com/operator-framework/operator-sdk/test/'.

[camilamacedo86]

HI @estroz and @joelanford,

IMO we must implement solutions idempotent for the tests which means that they should not rely on the Travis or make targets. So, if a developer run go tests ../... in the project it should call the tests that should be executed and finish with success what will not occur in this case.

However, it is addressed in the PR: https://github.com/operator-framework/operator-sdk/pull/3499/files

[camilamacedo86]

Otherwise, if we do not force as to follow up this kind of path then it contributes to the scenario where is not possible run the tests outside of the Travis (locally).

[estroz]

/lgtm

[jmrodri]

/lgtm

[camilamacedo86]

we do not need that we can use tc.TestSuffix