Merge package:matcher

[mosuem]

• Move and fix workflow files, labeler.yaml, and badges in the README.md
• Rev the version of the package, so that pub.dev points to the correct site
• Add a line to the changelog:

* Move to `dart-lang/test` monorepo.

• Add the package to the top-level readme of the monorepo:

| [matcher](pkgs/matcher/) | Support for specifying test expectations via an extensible Matcher class. Also includes a number of built-in Matcher implementations for common cases. | [![pub package](https://img.shields.io/pub/v/matcher.svg)](https://pub.dev/packages/matcher) |

• Important! Merge the PR with 'Create a merge commit' (enabling then disabling the Allow merge commits admin setting)
• Update the auto-publishing settings on https://pub.dev/packages/matcher/admin
• Add the following text to https://github.com/dart-lang/matcher/:'

> [!IMPORTANT]  
> This repo has moved to https://github.com/dart-lang/test/tree/master/pkgs/matcher

• Publish using the autopublish workflow
• Push tags to GitHub using git tag --list 'matcher*' | xargs git push origin
• Close open PRs in dart-lang/matcher with the following message:

Closing as the [dart-lang/matcher](https://github.com/dart-lang/matcher) repository is merged into the [dart-lang/test](https://github.com/dart-lang/test) monorepo. Please re-open this PR there!

• Transfer issues by running dart run pkgs/repo_manage/bin/report.dart transfer-issues --source-repo dart-lang/matcher --target-repo dart-lang/test --add-label package:matcher --apply-changes
• Archive https://github.com/dart-lang/matcher/

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

PR Health

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:matcher	0.12.17	ready to publish	matcher-v0.12.17
package:checks	0.3.1-wip	WIP (no publish necessary)
package:fake_async	1.3.2	already published at pub.dev
package:test	1.25.9-wip	WIP (no publish necessary)
package:test_api	0.7.4-wip	WIP (no publish necessary)
package:test_core	0.6.6-wip	WIP (no publish necessary)

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[jakemac53]

Not sure what is up with the CLA bot here, I checked one of the previous PRs and it said they had signed the CLA.

[devoncarew]

Not sure what is up with the CLA bot here, I checked one of the previous PRs and it said they had signed the CLA.

With these package move PRs, there's always a historical commit or two which triggers the CLA bot. Since the commits are all coming from existing dart-lang repos, it's OK to override the CLA bot (via the link given in the CLA status).