misc: add need-triage label as soon as the issue opens

[satyampsoni]

Description

Currently, the repository has hundreds of open issues, making it difficult to manage and prioritize them effectively. It’s challenging to identify which issues are ready to be worked on. This lack of clarity slows down the triage process and creates inefficiencies in maintaining the backlog.

To address this, I propose automatically adding the needs-triage label to an issue as soon as it is created. If the issue is deemed valid or a feature worth pursuing, the triage-accepted label can be added, and the needs-triage label removed. The needs-triage label will serve as an indicator for issues that have not yet been reviewed or approved for work. This approach will help the team systematically review and categorize issues, ensuring each one is evaluated for its relevance and priority. By leveraging the needs-triage label, we can enhance the visibility of untriaged issues, streamline the workflow, and maintain a more organized and actionable backlog.

Fixes #

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[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