Release workflow

[michael-valdron]

Please specify the area for this PR

ci
registry operator

What does does this PR do / why we need it:

Includes addition of a release workflow to automate the container image publication process.

If workflow is successful, it will create new release tags for quay.io/devfile/registry-operator and quay.io/devfile/registry-operator-bundle, release tags should be either v[0-9].[0-9].[0-9] or v[0-9].[0-9].[0-9]-rc.[0-9] pattern.

Which issue(s) this PR fixes:

Fixes #?

fixes devfile/api#1267

PR acceptance criteria:

• Test Coverage
  • Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?
• Gosec scans
  • Fix all MEDIUM and higher findings and/or annotate a finding per gosec instructions: https://github.com/securego/gosec#annotating-code to address why a finding is not a security issue

Documentation

• Does the registry operator documentation need to be updated with your changes?

How to test changes / Special notes to the reviewer:

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3fedd3e) 26.43% compared to head (dab9fda) 26.43%.

❗ Current head dab9fda differs from pull request most recent head 8aba019. Consider uploading reports for the commit 8aba019 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   26.43%   26.43%           
=======================================
  Files          25       25           
  Lines        1415     1415           
=======================================
  Hits          374      374           
  Misses       1020     1020           
  Partials       21       21           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[michael-valdron]

With these changes release tags trigger the "Release" workflow which first validates the places the version is defined and then pushes the images alongside running integration tests on k8s 1.25 & 1.26 (does not pass due to timeouts, see devfile/api#1313 for more details):

If version check fails, the other jobs do not run:

[michael-valdron]

OpenShift release testing PR: openshift/release#44995

[michael-valdron]

Documentation

Does the registry operator documentation need to be updated with your changes?

N/A

[michael-valdron]

Test Coverage

Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Integration testing in OpenShift passes, but on Kubernetes it times out. See devfile/api#1313.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michael-valdron, rm3l

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [michael-valdron,rm3l]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment