webrtc wpt: update rtp-payloadtypes test expectation

and reactivate test

BUG=webrtc:12194

Change-Id: Ie71da8834182ea458654d7b802dcdccd39fcd482
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2580532
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#836047}

third_party/blink/web_tests/TestExpectations

@@ -5881,6 +5881,3 @@ crbug.com/1156175 external/wpt/requestidlecallback/callback-iframe.html [ Pass T
 
 # Sheriff 2020-12-08
 crbug.com/1154178 external/wpt/webmessaging/broadcastchannel/basics.html [ Pass Failure ]
-
-# WebRTC: allow fix for bugs.webrtc.org/12194 to roll into chrome
-external/wpt/webrtc/protocol/rtp-payloadtypes.html [ Pass Failure ]

third_party/blink/web_tests/external/wpt/webrtc/protocol/rtp-payloadtypes-expected.txt

 This is a testharness.js-based test.
 PASS setRemoteDescription with a codec in the range 96-127 works
-FAIL setRemoteDescription with a codec in the range 35-63 works assert_true: expected true got false
+PASS setRemoteDescription with a codec in the range 35-63 works
 FAIL setRemoteDescription with a codec in the range 64-95 throws an InvalidAccessError assert_unreached: Should have rejected: undefined Reached unreachable code
 Harness: the test ran to completion.