Purpose

I've added a labeler.yml file to automate the process of applying labels to pull requests and issues based on file changes. The labeler will assign appropriate labels for changes related to documentation, tests, build configurations, and source code.

Description

Related Issue

Does this introduce a breaking change?

When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.

• Yes
• No

Type of change

• Bugfix
• Feature
• Code style update (e.g., formatting, local variables)
• Refactoring (no functional or API changes)
• Documentation content changes
• Other... Please describe: Add labeler.yml to automate labelling

Checklist

Before submitting your pull request, please confirm the following:

• I have thoroughly tested my changes: I confirm that I have run the code and manually tested all affected areas.
• All existing tests pass: I have run all tests and confirmed that nothing is broken.
• I have added new tests (if applicable): I have written tests that cover the new functionality introduced by my code changes.
• I have followed the Co-op Translators coding conventions: My code adheres to the style guide and coding conventions outlined in the repository.
• I have documented my changes (if applicable): I have updated the documentation to reflect the changes where necessary.

Additional context