ci: add PR labeler action

[snitin315]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make? (Give an overview)

Fix #16620

Is there anything you'd like reviewers to focus on?

Notes regarding pull_request_target event. It requires the workflow file to be present at the main branch.

For testing purposes, you can play create PRs in my forked repo - https://github.com/snitin315/eslint/pulls

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	d2f8a7a
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/65cfbaece37ec40008a9f47e

[eslint-github-bot]

Hi @snitin315!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[nzakas]

Thanks for looking into this! Just a few suggestions.

[harish-sethuraman]

we do already have the same label coming from our github bot. Should we do this from both the places or keep one alive?

[snitin315]

The bot attaches the label as per the PR title, it's fine to keep it at both places. Also, this is yet to be implemented in other eslint repositories.

[nzakas]

LGTM. Let's try it out and see how it goes. :)