Automate OLM V1 release

[dtfranz]

To help facilitate a simple and repeatable release process, tools should be created to automate it as much as possible. This automation should exist in whichever repository is chosen or created from #111.

When invoked it should create a new manifest containing the chosen versions of each sub-component, then make that manifest available for use.

Acceptance criteria:

• Automation (i.e. github action) is created for OLM V1 releases.
• The automation populates a manifest with the chosen versions of each OLM V1 sub-component.
• The chosen automation finally publishes the release.

[awgreene]

After a discussion on Slack, we've decided to treat each release of OLM V1 as an operator-controller release.

Marking this as obsolete and closing the issue.