Create labeler workflow.

[Hug0-Drelon]

Summary

Fixes #2484

Relevant technical choices

Using action/labeler pinned to v6.1.0 commit.
The labeler config file is put directly in .github/workflow directory, maybe not the best place.

Use of AI Tools

I used Cursor.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
Co-authored-by: mukeshpanchal27 <mukesh27@git.wordpress.org>
Co-authored-by: westonruter <westonruter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[mukeshpanchal27]

Nice ✨

[mukeshpanchal27]

@westonruter This PR only addresses half of the issue. Could we open a separate PR for the Assign Milestone part, or would you prefer to handle both fixes in a single PR?

[sarthak-19]

Rest LGTM !

[sarthak-19]

the workflow only runs on pull_request_target opened, so if a contributor pushes more commits, removes files, or changes plugin scope, labels will not update.

Suggested change

	- opened
	types:
	- opened
	- synchronize

[sarthak-19]

There is no branch filter, so this will run for PRs to any base branch.
We can limit the scope here ? @westonruter Any opinions ?

Suggested change

	branches:
	- trunk
	- 'release/**'
	- 'feature/**'