Establish a release planning process and cadence for team-OLM controlled upstream repositories (e.g. operator-lifecycle-manager, operator-registry, rukpak, etc...)

Acceptance Criteria:

• A hackmd describing:
    - process and guidelines for planning a release; i.e. WHAT gets into a release
    - a release cadence; i.e. WHEN it gets in
    - relationship w/ downstream Jira board; i.e. process for what we mirror into Jira (and from Jira -> upstream) – Note: it's also acceptable for the initial process to be downstream Jira-only for this spike

    - alternatives
    - (potentially) citations for where this cadence has been used in other projects

    - suggestions of where to codify the release process/cadence (e.g. README.md in each repo)
    - a set of story-templates to track each release with; e.g. "cut a release"
    - a set of stories to codify the process/cadence

Prior Art:

• https://github.com/operator-framework/operator-lifecycle-manager/pull/1812