clang-tidy: suppress cppcoreguidelines-init-variables

-ftrivial-auto-var-init is used to address uninitialized
POD variables.

Bug: 501491694
Change-Id: Ie381ae041953e8a9a2c43b6f1ddf8da60dde04c2
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/335675
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Shrek Shao <shrekshao@google.com>
Auto-Submit: Shrek Shao <shrekshao@google.com>

.clang-tidy

diff --git a/.clang-tidy b/.clang-tidy
index 6e9a21d..e73eef8 100644
--- a/.clang-tidy
+++ b/.clang-tidy
@@ -30,7 +30,6 @@
   ## P0. Most likely to help with hardening.
   #- -readability-inconsistent-declaration-parameter-name  # in webgpu.h and src/tint
   ## - Memory initialization
-  #- -cppcoreguidelines-init-variables  # has fixits
   #- -cppcoreguidelines-pro-type-member-init  # has fixits
   ## - Other memory safety
   #- -bugprone-casting-through-void
@@ -177,6 +176,8 @@
   - -readability-redundant-nested-if
 
   # P∞. Checks we're not really interested in re-enabling.
+  # -ftrivial-auto-var-init = pattern (debug) or zero (release) is enabled across chrome build, which addresses uninitialized issues of POD variables.
+  - -cppcoreguidelines-init-variables
   # - Appears unnecessary since we use hardened libc++.
   - -cppcoreguidelines-pro-bounds-avoid-unchecked-container-access
   # - Clang already catches the more problematic cases (& with ==, etc.) in