Roll BoringSSL from 298ac7850717 to b1ef5eee90d8 (4 revisions)

https://boringssl.googlesource.com/boringssl.git/+log/298ac7850717..b1ef5eee90d8

2025-03-10 ebiggers@google.com Fix missing vzeroupper in poly_Rq_mul()
2025-03-10 ebiggers@google.com Use vmovdqa to save/restore xmm registers in AES-GCM code on Windows
2025-03-10 ebiggers@google.com Fix missing vzeroupper in gcm_ghash_vpclmulqdq_avx2() for len=16
2025-03-10 ebiggers@google.com aes-gcm-avx10-x86_64.pl: use strict mode and sync with avx2 code

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/boringssl-chromium
Please CC boringssl-cabal@google.com,boringssl@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in BoringSSL: https://crbug.com/boringssl/new
To file a bug in Chromium: https://crbug.com/new

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: boringssl-cabal@google.com
Change-Id: Ib56ca9d9990666fee98a517ce484fac2a0345111
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6341006
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1430542}

DEPS

@@ -310,7 +310,7 @@ vars = {
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling BoringSSL
   # and whatever else without interference from each other.
-  'boringssl_revision': '298ac78507178d1e7d058eee1e52333f760eb0c1',
+  'boringssl_revision': 'b1ef5eee90d8748d5273fa3e6bb618dd4f925135',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling Fuchsia sdk
   # and whatever else without interference from each other.