Use different error messages for allowed vs suggested validation errors

actions-languageservice/src/validate.test.ts

@@ -75,7 +75,7 @@ jobs:
 
     expect(result.length).toBe(1);
     expect(result[0]).toEqual({
-      message: "Value 'does-not-exist' is not valid",
+      message: "Value 'does-not-exist' might not be valid",
       severity: DiagnosticSeverity.Warning,
       range: {
         end: {
@@ -108,7 +108,7 @@ jobs:
 
     expect(result.length).toBe(1);
     expect(result[0]).toEqual({
-      message: "Value 'does-not-exist' is not valid",
+      message: "Value 'does-not-exist' might not be valid",
       severity: DiagnosticSeverity.Warning,
       range: {
         end: {

actions-languageservice/src/validate.ts

@@ -157,11 +157,22 @@ async function additionalValidations(
 }
 
 function invalidValue(diagnostics: Diagnostic[], token: StringToken, kind: ValueProviderKind) {
-  diagnostics.push({
-    message: `Value '${token.value}' is not valid`,
-    severity: kind === ValueProviderKind.AllowedValues ? DiagnosticSeverity.Error : DiagnosticSeverity.Warning,
-    range: mapRange(token.range)
-  });
+  switch (kind) {
+    case ValueProviderKind.AllowedValues:
+      diagnostics.push({
+        message: `Value '${token.value}' is not valid`,
+        severity: DiagnosticSeverity.Error,
+        range: mapRange(token.range)
+      });
+      break;
+
+    case ValueProviderKind.SuggestedValues:
+      diagnostics.push({
+        message: `Value '${token.value}' might not be valid`,
+        severity: DiagnosticSeverity.Warning,
+        range: mapRange(token.range)
+      });
+  }
 }
 
 function getProviderContext(