feat(action): Improve bug report creation

[gauthierpetetin]

Description

The purpose of this improvement is to automate several steps that I currently do manually when a new release x.y.z is created:

1. Create regression labels on public code repo (metamask-extension) and private planning repo (MetaMask-planning)
   a. regression-RC-x.y.z
   b. regression-prod-x.y.z
2. Create bug report issue on planning repo
3. Add the bug report issue to the Releases Github Project board
4. Set the RC cut date on the Releases Github Project board.

These steps are important because the data pipelines of our metrics system consume the data that's present on the Releases Github Project board.

Finally this improvement includes a check to no longer re-create the bug report issue when it already exists, which used to happen sometimes when the release was re-cut, and which was disturbing other automations (e.g. wrong metrics, duplicated Slack notifications).

The following prerequisites are already met:

• Add BUG_REPORT_TOKEN to repo secrets (fine grained access token with Issues:Write and Metadata:Read permissions for metamask-mobile and mobile-planning repos, as well as Projects: Write permissions for MetaMask organization)
• Add RELEASES_GITHUB_PROJECT_BOARD_NUMBER to repo variables
• Add RELEASES_GITHUB_PROJECT_BOARD_VIEW_NUMBER to repo variables

Same PR for Extension

Related issues

None

Manual testing steps

1. Go to this public code repo (equivalent of metamask-extension repo)
2. Create a new branch with the following format: release/x.y.z (where x, y, z, are numbers)
3. Wait for 30s, until the Github action execution is finalised
4. Check that regression-RC-x.y.z and regression-prod-x.y.z labels have been created on the public code repo
5. Go to this private planning repo (equivalent of MetaMask-planning repo)
6. Check that regression-RC-x.y.z and regression-prod-x.y.z labels have been created on the private planning repo
7. Check that the bug report issue has been created on the private planning repo and has the following title: "vx.y.z Bug Report"
8. Go to this Github Project board
9. Check that the bug report issue is present on the board and its "RC Cut" date is set to the current date.

In case, you don't have sufficient permissions on these test repos, here's a video where the manual testing steps are demoed.

Screenshots/Recordings

Before

None

After

Github action to automate bug report creation - Watch Video

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Cal-L]

LGTM