[linter] Improve error handling when processing messages.yaml file.

Adds some missing `$`s to fix string interpolation when reporting
errors in the `messages.yaml` file. Also adds a try/catch so that if
an error occurs while processing a particular lint code, the lint code
in question will always be reported.

This should make it easier to track down problems when working on the
linter's `messages.yaml` file.

Change-Id: I6a6a6964072522ac4f43579f28f8d190a0c794f1
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451840
Auto-Submit: Paul Berry <[email protected]>
Reviewed-by: Samuel Rawlins <[email protected]>
Commit-Queue: Samuel Rawlins <[email protected]>

Author: stereotype441

pkg/linter/tool/messages_info.dart

@@ -47,7 +47,7 @@ final Map<String, RuleInfo> messagesRuleInfo = () {
   var lintCodes = messagesYaml['LintCode'] as YamlMap?;
   if (lintCodes == null) {
     throw StateError(
-      "The '_messagesFileName' file does not have a 'LintCode' section.",
+      "The '$_messagesFileName' file does not have a 'LintCode' section.",
     );
   }
 
@@ -57,7 +57,7 @@ final Map<String, RuleInfo> messagesRuleInfo = () {
     for (var i = 0; i < lintCodeKeys.length; i++) {
       if (lintCodeKeys[i] != lintCodeKeysSorted[i]) {
         throw StateError(
-          "The LintCode entries in '_messagesFileName' "
+          "The LintCode entries in '$_messagesFileName' "
           "are not sorted alphabetically, starting at '${lintCodeKeys[i]}'.",
         );
       }
@@ -77,7 +77,13 @@ final Map<String, RuleInfo> messagesRuleInfo = () {
     rule.addEntry(uniqueName, data);
   }
 
-  return builders.map((key, value) => MapEntry(key, value.build()));
+  return builders.map((key, value) {
+    try {
+      return MapEntry(key, value.build());
+    } catch (e, st) {
+      Error.throwWithStackTrace('Problem with lint code $key: $e', st);
+    }
+  });
 }();
 
 final String _messagesYamlPath = pathRelativeToPackageRoot(['messages.yaml']);