Disable a couple of devtools web_tests to allow landing a frontend change

Unfortunately the devtools frontend and a bunch of tests that check it
live in 2 separate repos (chromium.src and devtools_frontend), this
means that sometimes a frontend change will cause tests to fail, and the
only way to deal with this is first disable those tests in chromium.src
then land the frontend change, then go back, fix and re-enable those
tests.

This disables 2 color-swatch tests in order to land:
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2480042

Bug: 1137438
Change-Id: I0c81bc188260173f5b041dd53d63d866fabf43df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490282Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Patrick Brosset <patrick.brosset@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#819757}

third_party/blink/web_tests/TestExpectations

@@ -2465,6 +2465,10 @@ crbug.com/27659 external/wpt/css/css-ruby/ruby-line-breaking-003.html [ Failure
 crbug.com/27659 external/wpt/css/css-ruby/ruby-whitespace-001.html [ Failure ]
 crbug.com/27659 external/wpt/css/css-ruby/ruby-whitespace-002.html [ Failure ]
 
+# Disabling tests temporarily in order to land a devtools-frontend color-swatch change. Will re-enable soon.
+crbug.com/1137438 http/tests/devtools/elements/styles-1/color-swatch.js [ Failure Pass ]
+crbug.com/1137438 http/tests/devtools/elements/styles/url-color-swatch.js [ Failure Pass ]
+
 # WebRTC: Perfect Negotiation times out in Plan B. This is expected.
 crbug.com/980872 virtual/webrtc-wpt-plan-b/external/wpt/webrtc/RTCPeerConnection-perfect-negotiation.https.html [ Timeout ]