Run same tests for layout-2020 and layout-2013 (#30092)

Most tests were only being run for layout-2013, not for layout-2020.
This wasn't great since layout-2020 is now the default.

So this patch unifies the lists of included tests for both layouts.
For layout-2013 this implies adding css/css-content/, css/css-logical/
and css/css-masking/clip/.
For layout-2020 this implies adding several additional css tests, and
also tests like dom/, js/, html/, etc.

tests/wpt/meta/html/browsers/the-windowproxy-exotic-object/windowproxy-prototype-setting-cross-origin-domain.sub.html.ini

@@ -0,0 +1,18 @@
+[windowproxy-prototype-setting-cross-origin-domain.sub.html]
+  [Cross-origin via document.domain: the prototype is null]
+    expected: FAIL
+
+  [Cross-origin via document.domain: setting the prototype to an empty object via __proto__ should throw a "SecurityError" DOMException]
+    expected: FAIL
+
+  [Cross-origin via document.domain: the prototype must still be null]
+    expected: FAIL
+
+  [Cross-origin via document.domain: setting the prototype to null via Object.setPrototypeOf should not throw]
+    expected: FAIL
+
+  [Cross-origin via document.domain: setting the prototype to null via __proto__ should throw a "SecurityError" since it ends up in CrossOriginGetOwnProperty]
+    expected: FAIL
+
+  [Cross-origin via document.domain: setting the prototype to null via Reflect.setPrototypeOf should return true]
+    expected: FAIL

tests/wpt/meta/html/browsers/the-windowproxy-exotic-object/windowproxy-prototype-setting-cross-origin.sub.html.ini

@@ -0,0 +1,18 @@
+[windowproxy-prototype-setting-cross-origin.sub.html]
+  [Cross-origin: the prototype is null]
+    expected: FAIL
+
+  [Cross-origin: setting the prototype to an empty object via __proto__ should throw a "SecurityError" DOMException]
+    expected: FAIL
+
+  [Cross-origin: the prototype must still be null]
+    expected: FAIL
+
+  [Cross-origin: setting the prototype to null via Object.setPrototypeOf should not throw]
+    expected: FAIL
+
+  [Cross-origin: setting the prototype to null via __proto__ should throw a "SecurityError" since it ends up in CrossOriginGetOwnProperty]
+    expected: FAIL
+
+  [Cross-origin: setting the prototype to null via Reflect.setPrototypeOf should return true]
+    expected: FAIL

tests/wpt/meta/html/browsers/the-windowproxy-exotic-object/windowproxy-prototype-setting-goes-cross-origin-domain.sub.html.ini

@@ -0,0 +1,27 @@
+[windowproxy-prototype-setting-goes-cross-origin-domain.sub.html]
+  [Became cross-origin via document.domain: the prototype is now null]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to an empty object via __proto__ should throw a "SecurityError" DOMException]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: the prototype must still be null]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to null via Object.setPrototypeOf should not throw]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to null via __proto__ should throw a "SecurityError" since it ends up in CrossOriginGetOwnProperty]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to null via Reflect.setPrototypeOf should return true]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to the original value from before going cross-origin via Object.setPrototypeOf should throw a TypeError]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to the original value from before going cross-origin via __proto__ should throw a "SecurityError" DOMException]
+    expected: FAIL
+
+  [Became cross-origin via document.domain: setting the prototype to the original value from before going cross-origin via Reflect.setPrototypeOf should return false]
+    expected: FAIL