Enable google-upgrade-googletest-case clang-tidy check

Following this discussion on cxx[1], this CL enables
google-upgrade-googletest-case clang-tidy check in Tricium.

For the existing warnings from Chromium, they’ve been fixed at [2].

[1] https://groups.google.com/a/chromium.org/g/cxx/c/IW9mSXaoV08/m/Yd7tYtQOAQAJ
[2] https://chromium-review.googlesource.com/c/chromium/src/+/5220291

Bug: 1520202, 1474588
Change-Id: I7fc5559d3828d393f2240cac6ddf7dac0433fa6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5220311
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1251285}

.clang-tidy

@@ -18,6 +18,7 @@
                     google-default-arguments,
                     google-explicit-constructor,
                     google-objc-avoid-nsobject-new,
+                    google-upgrade-googletest-case,
                     misc-misleading-identifier,
                     misc-homoglyph,
                     modernize-avoid-bind,

base/win/.clang-tidy

@@ -7,6 +7,7 @@ Checks: '-*,
          google-build-namespaces,
          google-default-arguments,
          google-readability-namespace-comments,
+         google-upgrade-googletest-case,
          modernize-avoid-bind,
          modernize-concat-nested-namespaces,
          modernize-make-shared,