Print internal errors using GitHub problem matchers

Internal errors (explanations of known problematic cases or an
unexpected result) should be printed more clearly so that triaging can
go quicker. Add a tag to print_red() and print_yellow() so that a
problem matcher can print them automatically, making it clear what
happened with the build.

Signed-off-by: Nathan Chancellor <[email protected]>

Author: nathanchance

.github/problem-matchers/internal.json

@@ -0,0 +1,16 @@
+{
+    "problemMatcher": [
+        {
+            "__comment_owner": "internal continuous integration errors",
+            "owner": "internal",
+            "pattern": [
+                {
+                    "__comment_regexp1": "[CI ERROR] Build is not finished on TuxSuite's side!",
+                    "regexp": "^\\[CI (WARNING|ERROR)\\]\\s+(.*)$",
+                    "severity": 1,
+                    "message": 2
+                }
+            ]
+        }
+    ]
+}

utils.py

@@ -290,12 +290,12 @@ def update_repository_variable(
 
 
 def print_red(msg):
-    print(f"\033[91m{msg}\033[0m", file=sys.stderr)
+    print(f"\033[91m[CI ERROR] {msg}\033[0m", file=sys.stderr)
     sys.stderr.flush()
 
 
 def print_yellow(msg):
-    print(f"\033[93m{msg}\033[0m", file=sys.stdout)
+    print(f"\033[93m[CI WARNING] {msg}\033[0m", file=sys.stdout)
     sys.stdout.flush()