ci: update ngbot config for L1 triage

[ocombe]

PR Type

What kind of change does this PR introduce?

[x] CI related changes

What is the current behavior?

No config for L1 triage

Issue Number: #23072

What is the new behavior?

Added config for L1 triage, and refactored parameter name for L2 triage

Does this PR introduce a breaking change?

[x] No

[manughub]

Need to think through the state of an issue once L2 triage is done so we dont keep going back and forth. Will update. Pls hold off on merging this. I'll update the outcome here.

[manughub]

Summary of what we'll need: @ocombe

A new issue/feature-request that gets logged (ie that does not yet have comp), will not get a milestone.

An open issue that has a comp and is missing either severity, type or freq will have a milestone:needsTriage.
An open feature request that has a comp and is missing type (freq and severity are not applicable for feature) will have milestone:needsTriage.

Once an issue has comp, type, severity and freq then its milestone:backlog
Once a feature has comp, type type then its milestone:backlog

[manughub]

Seems to be working fine, however the updates prior to this PR have left some of the issues in an inconsistent state. Looks like the bot is not crawling the full set of issues to do a clean up based on changes we made.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}