Improve Report release vulnerabilities action

[SaschaSchwarze0]

Changes

In this PR, I ...

• split the action which so far only ran a single script into two scripts: the first script downloads the latest release and determines details (tag, branch, go-version), the second script scans for vulnerabilities, checks if a rebuild fixes them and if that is the case triggers a release
• extend the action so that after the first script it clones the release branch and also calls setup-go again to use the Go version from the release branch
• reschedule the action to start 15 minutes after the base image build (which usually takes between four and five minutes to complete)
• assign the created issue to the users listed as approvers in the OWNERS file

I tested the scripts and their commands, but I cannot test the overall action anywhere as I don't have the necessary releases in a fork.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

Release Notes

NONE

[adambkaplan]

/approve

Only one suggestion, otherwise looks good to the extent of my abilities reading bash scripts (which is not great).

Any way to test this beyond "push and pray"?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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 [adambkaplan]

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

[HeavyWombat]

/lgtm