Deprecate the export of package:matcher APIs

[natebosch]

Tests should import the matching framework, either
package:matcher/expect.dart, or package:checks/checks.dart, or some
third party alternative.

• Add fix data for every member of package:matcher/expect.dart to
  replace the member with the package:test/test.dart URI.
• Mark the export deprecated`.
• Add a library directive so the deprecation annotation is
  unambiguously applied to the export and not the entire library.
• Apply bulk fixes in tests. This adds the matcher dependency and
  import. Manually sort dependencies to satisfy a separate lint.

[github-actions]

PR Health

[natebosch]

@keertip @bwilkerson - Is there a way to handle a class moved to a different import?

This seems to be working well to use replacedBy for the top level functions and variables, but I cannot find any allowed configuration which handles the moved classes.

A change of type 'replacedBy' can't be used for an element of kind 'class'

[bwilkerson]

It appears that we don't currently support using replacedBy with class-like declarations.

I know that at one point we discussed adding a movedTo transform that would support moving top-level declarations to a different library, but it looks like we haven't implemented that yet.

[natebosch]

I filed dart-lang/sdk#57057 to track. Either solution sounds great.