Move pkg/predicate closer to where it is used.

[jmrodri]

Description of the change:
Move pkg/predicate to the ansible package because it is not used anywhere else.

Motivation for the change:
Since this package is not used outside the ansible package, it makes sense to have it co-located. In the future we hope to move it to operator-lib or controller-runtime.

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

[fabianvf]

/lgtm

[joelanford]

/lgtm

[joelanford]

Just double checking... Is the upstream predicate the same as the one the ansible operator was using? The ansible e2e test keeps failing.

[jmrodri]

GenerationChangedPredicate is slightly different between the 2 implementations:

The one in SDK https://github.com/operator-framework/operator-sdk/blob/master/pkg/predicate/predicate.go#L56-L59:

	if e.MetaNew.GetGeneration() == e.MetaOld.GetGeneration() && e.MetaNew.GetGeneration() != 0 {
		return false
	}
	return true

And the one from controller-runtime is simpler https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/predicate/predicate.go#L181:

	return e.MetaNew.GetGeneration() != e.MetaOld.GetGeneration()

So looks like by using the upstream version we introduced a regression fixed by PR #2830 and identified by Issue #2108.

[jmrodri]

Closing in favor of PR #3532