Catalog source polling interval not always set by typed client

[exdx]

Bug Report

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).

Seems like the custom unmarshalling of catalog sources polling intervals introduced by operator-framework/api#169 leads to the catalog source typed client not always applying the catalog source correctly. The catalog source gets created without an polling interval set some of the time, even though one should always be applied. This affects the catalog polling e2e test as well as potentially impact custom catalogs that have polling intervals set.

Using kubectl versus the typed client does not cause this issue to occur.

The workaround done downstream was to provide a RawInterval instead, which then does not cause this issue to occur. See 573cccd

What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
Catalogsources are created with a polling interval consistently set.

What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Catalogsources are sometimes created without a polling interval set using the typed client.

Environment

• operator-lifecycle-manager version:

• Kubernetes version information:

• Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

[exdx]

This issue only affects the OLM test since it is relying on the catalog source versioned client, which only OLM uses. Using other clients such as the standard or dynamic client does not result in this issue occurring.

If this issue manifests itself when OLM creates other resources then it may make sense to increment severity and triage.