feat(ci): Auto add needs-triage label on bug open

[desi]

Description

We use the stale bot in order to make sure we close out issues which have been open and waiting on additional information from reporters for too long. However, sometimes this can be the case for issues that we just haven't had an opportunity to follow back up on. We feel a couple of process improvements can make this better.

Related issues

Partially fixes: https://github.com/MetaMask/MetaMask-planning/issues/4219

Related to:
https://github.com/MetaMask/github-tools/pull/41/files
MetaMask/metamask-extension#30512

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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

[gauthierpetetin]

LGTM!