fix(bug report): description was inaccurate

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

@@ -23,7 +23,7 @@ jobs:
           payload=$(cat <<EOF
           {
             "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.",
+            "body": "This bug report was automatically created by a GitHub action upon the creation of release branch \`release/${{ env.version }}\` (release cut).\n\nNote that once the release is prepared for store submission, meaning the \`release/${{ env.version }}\` branch merges into \`main\`, another GitHub action will automatically close this epic.\n\n**What is it used for?**\n\n1. It is used to track release dates on this [Github Project board](https://github.com/orgs/MetaMask/projects/86/views/3). Release dates are then pulled into our metrics system.\n\n2. It is also used by our Zapier automations, in order to know if automated automations shall be sent on Slack for the given release. Notifications will only be sent if this issue is open.",
             "labels": ["type-bug", "team-mobile-platform", "regression-RC-${{ env.version }}"]
           }
           EOF