Disable some of the QUIC end-to-end tests in Chrome.

Those tests appear to randomly fail on ChromeOS trybot, most likely as a consequence of cl/465535182.

PiperOrigin-RevId: 466353607

quiche/quic/core/http/end_to_end_test.cc

diff --git a/quiche/quic/core/http/end_to_end_test.cc b/quiche/quic/core/http/end_to_end_test.cc
index 50fe6a3..6a6161d 100644
--- a/quiche/quic/core/http/end_to_end_test.cc
+++ b/quiche/quic/core/http/end_to_end_test.cc
@@ -3872,7 +3872,9 @@
   }
 };
 
-TEST_P(EndToEndTest, AckNotifierWithPacketLossAndBlockedSocket) {
+// TODO(b/241910187): re-enable this test in Chrome.
+TEST_P(EndToEndTest, QUICHE_TEST_DISABLED_IN_CHROME(
+                         AckNotifierWithPacketLossAndBlockedSocket)) {
   // Verify that even in the presence of packet loss and occasionally blocked
   // socket, an AckNotifierDelegate will get informed that the data it is
   // interested in has been ACKed. This tests end-to-end ACK notification, and
@@ -3975,7 +3977,8 @@
 }
 
 // Send a public reset from the server.
-TEST_P(EndToEndTest, ServerSendPublicReset) {
+// TODO(b/241910187): re-enable this test in Chrome.
+TEST_P(EndToEndTest, QUICHE_TEST_DISABLED_IN_CHROME(ServerSendPublicReset)) {
   ASSERT_TRUE(Initialize());
 
   EXPECT_TRUE(client_->client()->WaitForOneRttKeysAvailable());