[BoringSSL] Update third_party/boringssl-with-bazel

[veblush]

Change was created by the release automation script. See go/grpc-release.

On top of changes made by the script, setup.py had to be updated to have /std:c11 option for MSVC to use c11 features for boringssl.

[veblush]

Distribution Test Python MacOS failed with the following error (log)

clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
Apple clang version 14.0.0 (clang-1400.0.29.202)
Target: x86_64-apple-darwin21.6.0

[gnossen]

LGTM to setup.py changes.

[veblush]

Distribution Test Python MacOS failed with the following error (log)

clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
Apple clang version 14.0.0 (clang-1400.0.29.202)
Target: x86_64-apple-darwin21.6.0

This turned out to be caused by OOM so I reduce the -j value from 4 to 2 to workaround it.

[Jan-E]

@veblush To make sure c11 is used with MSVC you could also add that to config.w32. Something like

 if (PHP_GRPC != "no") {
+ 
+  ADD_FLAG("CFLAGS_GRPC", " /std:c11 ");

This in reaction to what was there in the 1.61.0 release
https://github.com/google/boringssl/blob/2ff4b968a7e0cfee66d9f151cb95635b43dc1d5b/src/crypto/internal.h#L142
// TODO(davidben): In MSVC 2019 16.8 or higher (_MSC_VER >= 1928),
// |STDC_VERSION| will be 201112 when passed /std:c11 and unset otherwise.
// C11 alignas and alignof are only implemented in C11 mode. Can we mandate C11
// mode for those versions?