feat(.github/actions): add get-issue-url-and-version-number-v1 action

[Zidious]

This PR add an action that gets the issue URL And version number from the release-candidate issue and e.g. use for posting slack notifications. Adding this small GHA here means it lives in once place as it will be added to 5+ repositories.

Example workflow file:https://github.com/dequelabs/zidious-testing/actions/runs/6696030017/workflow
Example workflow: https://github.com/dequelabs/zidious-testing/actions/runs/6696030017/job/18192888009

Closes: #63, #82

Resolved

[straker]

I know this is small but I think this should be a typescript file and include tests. is-release-in-progress doesn't do too much more but does have tests.

This also doesn't need to be a composite action anymore as it only has the 1 step.

Resolved

[Zidious]

Re-ran test worflow: https://github.com/dequelabs/zidious-testing/actions/runs/6721071926/job/18265974025

Resolved

Resolved

[straker]

We are changing how we are doing this. Instead of opening the QA ticket from the create-release-candidate action, we'll be creating a new action that is run on push to release branch that will build and deploy the release, then we will create the QA ticket. Since we'll be in the branch that has all the information, we don't need to look for tickets and can just use the version from package.json and the current commit sha to put into the ticket.

[dequejenn]

We do need this, as we are not creating the issue during this step. We are creating the issue in create-release-candidate and then adding a comment to it, moving the issue around, and sending to slack in deploy-release-candidate

[straker]

Scope change:

1. We don't need to get the version number. At any point we would call this we can just look at the version of package.json in the current repo
2. For the docs repo there can be multiple open issues labeled release, either for different repos or even the same repo if multiple versions were released in quick succession and the docs for the prior one haven't been written yet. We'll need to filter all the open release issues by the name of the github repo and also by the current version. Allow supplying version number to input but default to current version from package.json
3. We'll need to allow the action to get issues from other repos (namely the docs repo). Add input for repo (default to current context repo)
4. Rename action to get-release-issue

[straker]

(see prior comment)

[Zidious]

Superseded by: #101