Bound terminal UTF-8 profile paths

Use an explicit source delimiter for terminal POSIX profile names so international names do not depend on ASCII word-boundary behavior.

Author: VladimirBrejcha

public-source-release-audit/scripts/check_current_source.rb

@@ -13,7 +13,7 @@
       (?:
         (?:/|\\/)
         (?:
-          (?:Users|home)(?:/|\\/)[A-Za-z0-9._\x80-\xFF-]+(?:(?:/|\\/)|\b)
+          (?:Users|home)(?:/|\\/)[A-Za-z0-9._\x80-\xFF-]+(?:(?:/|\\/)|(?=[<>"'\s,;:)\]\}]|\z))
           |
           root(?:(?:/|\\/)|(?![A-Za-z0-9._-]))
           |

public-source-release-audit/tests/test_check_current_source.rb

@@ -166,6 +166,7 @@ def test_supported_high_confidence_formats_are_detected_and_redacted
         "macos-root-home.txt" => "/" + "var/root/.ssh/id_ed25519",
         "macos-private-root-home.txt" => "/" + "private/var/root/.ssh/id_ed25519",
         "unicode-posix-home.txt" => "/" + "home/山田/private.txt",
+        "terminal-unicode-posix-home.txt" => "/" + "home/山田\n",
         "file-uri-home.txt" => "file://" + "/" + "home/example/private.txt",
         "windows-home.txt" => "C:" + "\\Users\\example\\private.txt",
         "lowercase-windows-home.txt" => "c:" + "\\users\\example\\private.txt",