Add time-based install/upgrade policy

[tmshort]

Follow-on to #235 Based on #232

Background As a user, I want to restrict when upgrades and installations occur. For instance, to off-hours (e.g. after 9pm) or on specific days (e.g. Sundays). This should be flexible enough to specify multiple days and hours.

Acceptance Criteria

• Add a time/day entry into the OperatorPolicy CR
• Add code to support the time/day entry, kicking off operator resolution when a valid time is reached.
• Unit/e2e-tests that verify desired behavior.
• Demonstrate that upgrades do not occur except when the

[yuriolisa]

Can I work on this one?

[joelanford]

@yuriolisa - Thanks for offering to help out!

However, IMO this should not be a core feature of OLM, and I think we should actually just close this issue. Core OLMv1 will allow declaratively setting a desired version, so I think a feature like this is best left to a separate extension that can integrate with the catalog and modify ClusterExtension objects per whatever policy is exposed by that extension.

Regardless, we certainly should not do this prior to 1.0.0. We are trying to keep the scope of that as small as possible and thus avoid adding features that we would have to maintain indefinitely.

If you see something you'd like to contribute to with the label v1.0 or that is not related to a user-facing feature, those would be better places to start!

[tmshort]

No intent to do this.