[Github workflow] Creation of qa automation tasks

[IsaSih]

Fixes rancher/qa-tasks#2164

Summary

This is a github workflow that is triggered every time a contributor of the dashboard repo labels an issue from the rancher/dashboard repo with the 'candidate-automation' label, or comments in this issue one of the strings '/ac', '/automation-candidate ', or '/automation'. The purpose of this workflow is to automate the creation of issues in the rancher/qa-tasks repo to track automated test coverage efforts corresponding to the original issue. This workflow is mainly intended to be used by the QA team during QA Reviews, but it can be triggered by any contributors to the rancher/dashboard repo, as soon as they identify that the issue is an automation candidate for the qa team to add automated e2e tests.

Areas or cases that should be tested

• Being a member of the rancher/dashboard repo and triggering the workflow by adding the 'candidate-automation' label, and verifying that the issue gets created in the 'rancher/qa-tasks' repo
• Being a member of the rancher/dashboard repo and triggering the workflow by commenting '/ac', and verifying that the issue gets created in the 'rancher/qa-tasks' repo.
• Being a member of the rancher/dashboard repo and triggering the workflow by commenting '/automation-candidate', and verifying that the issue gets created in the 'rancher/qa-tasks' repo.
• Being a member of the rancher/dashboard repo and triggering the workflow by commenting '/automation', and verifying that the issue gets created in the 'rancher/qa-tasks' repo.
• Not being a member of the rancher/dashboard repo and triggering the workflow by commenting or labelling the issue, and verifying that the issue does NOT get created in the 'rancher/qa-tasks' repo, and that the github-bot correctly comments in the original issue body that the workflow fails to create the issue because the user is not a member of the dashboard repo.
• [Optional]: Being a member of the rancher/dashboard repo and triggering the workflow locally with an expired token to induce a generic workflow failure and verifying that the issue does NOT get created in the 'rancher/qa-tasks' repo, and that the github-bot correctly comments in the original issue body that the workflow fails to create the issue because of a generic workflow failure.

Areas which could experience regressions

Maybe other existing github workflows.

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[richard-cox]

I've added QA/None to work resolve one of the blocking gates (all prs must link to a r/d issue). The other is blocked given there's unticked checkboxes in the description

[richard-cox]

I've dug into the actual script, but no objections my side for the workflow to merge