deps: update googletest to a newer commit

[dneto0]

The DEPS file pins googletest to an old specific commit.
I recall doing that because of unwanted build breakages.

Other contraints:

• We also wanted to make sure that developers would only need a compiler that could compile C++11. That means no later than googletest v1.12.1
  • However, the supported / tested compilers can all do much better than just C++11. We can allow requiring later versions of C++11. I think the major constraint here is needing to work with VS 2017.
• We prefer to avoid requiring extra dependencies like abseil. We don't need very fancy features of googletest. Just very old things.

[dneto0]

When I update to top-of-tree googletest, the bazel build fails.
Because the googletest BUILD.bazel file doesn't specify -std=c++14 when needed. google/googletest#4098
I have a fix in flight: google/googletest#4100

[dneto0]

Heh. Googletest depends on abseil now, and Abseil's rules for API stability but no ABI stability mean you're not supposed to set C++ standard inside the Bazel file. Instead do it on the command line.

See https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/abseil-cpp/FAQ.md#how-to-i-set-the-c_dialect-used-to-build-abseil