[analyzer] Add name and token to ExpectedType enum.

Changes the analyzer's `ExpectedType` enum (which is used for runtime
type checks of parameters to diagnostic messages) so that it includes
the types `name` and `token`. These correspond with types used in
parser error reporting.

In a future CL, I will be adding `parameters` declarations to
`pkg/front_end/messages.yaml`, following a similar format to the
format used by `pkg/analyzer/messages.yaml`. When that happens, the
analyzer's diagnostic message code generator will start trying to
generate runtime type checking code for parameters of type `name` and
`token`. Landing this change now ensures that when the new runtime
type checking code gets generated, it will work properly.

Change-Id: I6a6a69648c2fdff63d93da5c5c39ba75f65edc9c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/448248
Reviewed-by: Konstantin Shcheglov <[email protected]>
Commit-Queue: Paul Berry <[email protected]>

Author: stereotype441

pkg/_fe_analyzer_shared/lib/src/base/errors.dart

@@ -619,7 +619,7 @@ base mixin DiagnosticWithoutArguments on DiagnosticCode
 }
 
 /// Expected type of a diagnostic code's parameter.
-enum ExpectedType { element, int, object, string, type, uri }
+enum ExpectedType { element, int, name, object, string, token, type, uri }
 
 /// Interface for a diagnostic that does not have any unfilled template
 /// parameters, and hence is ready to be associated with a location in the

pkg/analyzer/lib/src/error/listener.dart

@@ -126,8 +126,10 @@ Expected types: $expectedTypes''');
     var typeMatches = switch (expectedTypes[i]) {
       ExpectedType.element => argument is Element,
       ExpectedType.int => argument is int,
+      ExpectedType.name => argument is String,
       ExpectedType.object => true,
       ExpectedType.string => argument is String,
+      ExpectedType.token => argument is Token,
       ExpectedType.type => argument is DartType,
       ExpectedType.uri => argument is Uri,
     };