Add explicit indicators for diagnostics that are missing documentation

I believe that this will make it easier to identify which diagnostics
are undocumented (though I haven't done this for parser-produced
diagnostics). It will also allow us to easily count how many there are
in order to monitor progress / regress.

I also normalized the location of the flag to make the file a little
cleaner.

Change-Id: I4fe07f446508788a8c02efcd8e78e94689ffb40b
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/365283
Reviewed-by: Samuel Rawlins <[email protected]>
Commit-Queue: Brian Wilkerson <[email protected]>

Author: bwilkerson

pkg/analyzer/lib/src/error/codes.g.dart

@@ -267,7 +267,7 @@ class CompileTimeErrorCode extends AnalyzerErrorCode {
     'AUGMENTATION_WITHOUT_LIBRARY',
     "The URI does not resolve to a library.",
     correctionMessage:
-        "Try updating the URI to reference the augmented library",
+        "Try updating the URI to reference the augmented library.",
   );
 
   ///  No parameters.
@@ -2128,10 +2128,10 @@ class CompileTimeErrorCode extends AnalyzerErrorCode {
   static const CompileTimeErrorCode GENERIC_FUNCTION_TYPE_CANNOT_BE_BOUND =
       CompileTimeErrorCode(
     'GENERIC_FUNCTION_TYPE_CANNOT_BE_BOUND',
-    "Generic function types can't be used as type parameter bounds",
+    "Generic function types can't be used as type parameter bounds.",
     correctionMessage:
         "Try making the free variable in the function type part of the larger "
-        "declaration signature",
+        "declaration signature.",
   );
 
   ///  It is a compile-time error if a generic function type is used as an actual