fix(rc issues): better handle RC issues

.github/scripts/check-template-and-add-labels.ts

@@ -326,7 +326,7 @@ async function userBelongsToMetaMaskOrg(
 function isReleaseCandidateIssue(
   issue: Labelable,
 ): boolean {
-  return Boolean(issue.labels.find(label => label.name === 'regression-RC'));
+  return Boolean(issue.labels.find(label => label.name.startsWith('regression-RC')));
 }
 
 // This function checks if issue belongs to a team not using templates.

.github/workflows/create-bug-report.yml

@@ -24,7 +24,7 @@ jobs:
           {
             "title": "v${{ env.version }} Bug Report",
             "body": "This bug report was automatically created by a GitHub action upon the creation of release branch \`Version-v${{ env.version }}\` (release cut).\n\n**Expected actions for release engineers:**\n\n1. Convert this issue into a Zenhub epic and link all bugs identified during the release regression testing phase to this epic.\n\n2. After completing the first regression run, move this epic to \"Regression Completed\" on the [Extension Release Regression board](https://app.zenhub.com/workspaces/extension-release-regression-6478c62d937eaa15e95c33c5/board?filterLogic=any&labels=release-${{ env.version }},release-task).\n\nNote that once the release is prepared for store submission, meaning the \`Version-v${{ env.version }}\` branch merges into \`master\`, another GitHub action will automatically close this epic.",
-            "labels": ["type-bug", "regression-RC", "release-${{ env.version }}"]
+            "labels": ["type-bug", "team-mobile-platform", "regression-RC-${{ env.version }}"]
           }
           EOF
           )