Update package version to 148.0.7778.167

source-files/chromium-145-drop-unknown-clang-flag.patch

@@ -1,9 +1,11 @@
---- a/build/config/compiler/BUILD.gn      2026-03-09 19:52:01.000000000 +0000
-+++ b/build/config/compiler/BUILD.gn      2026-03-10 22:29:51.892264280 +0000
-@@ -1855,18 +1855,6 @@ config("sanitize_c_array_bounds") {
-     cflags = [
-       "-fsanitize=array-bounds",
-       "-fsanitize-trap=array-bounds",
+--- a/build/config/compiler/BUILD.gn
++++ b/build/config/compiler/BUILD.gn
+@@ -1903,20 +1903,4 @@ config("sanitize_c_array_bounds") {
+ config("sanitize_c_array_bounds") {
+   if (!is_ubsan && is_clang && !(is_asan && target_cpu == "x86")) {
+-    cflags = [
+-      "-fsanitize=array-bounds",
+-      "-fsanitize-trap=array-bounds",
 -
 -      # Some code users feature detection to determine if UBSAN (or any
 -      # sanitizer) is enabled, they then do expensive debug like operations. We
@@ -16,6 +18,6 @@
 -      # since we know that the array bounds sanitizing will catch any out-of-
 -      # bounds accesses.
 -      "-Wno-unsafe-buffer-usage-in-static-sized-array",
-     ]
+-    ]
    }
  }