Enable scenario test for L4S

The fix has landed.

Bug: webrtc:42225697, webrtc:383078466
Change-Id: I9838c9ed582ddef05d5d1593c5a3e6d9a60543aa
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/396802
Reviewed-by: Per Kjellander <perkj@webrtc.org>
Commit-Queue: Per Kjellander <perkj@webrtc.org>
Auto-Submit: Harald Alvestrand <hta@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#44955}
diff --git a/test/peer_scenario/tests/l4s_test.cc b/test/peer_scenario/tests/l4s_test.cc
index ce110f9..378ea2e 100644
--- a/test/peer_scenario/tests/l4s_test.cc
+++ b/test/peer_scenario/tests/l4s_test.cc
@@ -185,11 +185,7 @@
 
   s.ProcessMessages(TimeDelta::Seconds(2));
   EXPECT_GT(send_node_feedback_counter.FeedbackAccordingToRfc8888(), 0);
-  // TODO: bugs.webrtc.org/42225697 - Fix bug. Caller sends both transport
-  // sequence number feedback and congestion control feedback. So
-  // callee still send packets with transport sequence number header extensions
-  // even though it has been removed from the answer.
-  // EXPECT_EQ(send_node_feedback_counter.FeedbackAccordingToTransportCc(), 0);
+  EXPECT_EQ(send_node_feedback_counter.FeedbackAccordingToTransportCc(), 0);
 
   EXPECT_GT(ret_node_feedback_counter.FeedbackAccordingToRfc8888(), 0);
   EXPECT_EQ(ret_node_feedback_counter.FeedbackAccordingToTransportCc(), 0);