Add bug and triage label for bug reports on creation

[kevintab95]

Overview

1. This PR fixes or fixes part of #[NA].
2. This PR does the following: This PR edits the issue template for "bug report" to automatically add the "bug" and "triage needed" labels on creation. On a rota basis, a triager will look at bugs created in this manner and assign relevant labels based on their evaluation.

Changes to the template are made per https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository

Essential Checklist

• [ ] The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• [x] The linter/Karma presubmit checks have passed locally on your machine.
• [x] "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)
  • This lets reviewers restart your CircleCI tests for you.
• [x] The PR is made from a branch that's not called "develop".

Proof that changes are correct

This does not affect user facing behaviour. So this section is not relevant for the PR.

Proof of changes on desktop with slow/throttled network

This does not affect user facing behaviour. So this section is not relevant for the PR.

Proof of changes on mobile phone

Proof of changes in Arabic language

This does not affect user facing behaviour. So this section is not relevant for the PR.

PR Pointers

• Make sure to follow the instructions for making a code change.
• If you need a review or an answer to a question, and don't have permissions to assign people, leave a comment like the following: "{{Question/comment}} @{{reviewer_username}} PTAL". Oppiabot will help assign that person for you.
• For what code owners will expect, see the Code Owner's wiki page.
• Make sure your PR follows conventions in the style guide, otherwise this will lead to review delays.
• Never force push. If you do, your PR will be closed.
• Some of the e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.

[oppiabot[bot]]

Hi, @kevintab95, this pull request does not have a "CHANGELOG: ..." label as mentioned in the PR pointers. Assigning @kevintab95 to add the required label. PRs without this label will not be merged. If you are unsure of which label to add, please ask the reviewers for guidance. Thanks!

[oppiabot[bot]]

Hi @kevintab95, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

[oppiabot[bot]]

Hi, @kevintab95, this pull request does not have a "CHANGELOG: ..." label as mentioned in the PR pointers. Assigning @kevintab95 to add the required label. PRs without this label will not be merged. If you are unsure of which label to add, please ask the reviewers for guidance. Thanks!

[U8NWXD]

Lets hold off on this for a few days while the core maintainers discuss

[oppiabot[bot]]

Hi @kevintab95, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

[oppiabot[bot]]

Hi @kevintab95, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue. If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

[oppiabot[bot]]

Hi @kevintab95, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!