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/windows/browsing-context-names/choose-default-001.html.ini

@@ -0,0 +1,3 @@
+[choose-default-001.html]
+  [A embedded browsing context has empty-string default name]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/browsing-context.html.ini

@@ -0,0 +1,6 @@
+[browsing-context.html]
+  [Check that browsing context has new, ready HTML document]
+    expected: FAIL
+
+  [Check the document properties corresponding to the creator browsing context]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/dangling-markup-window-name.tentative.html.ini

@@ -0,0 +1,2 @@
+[dangling-markup-window-name.tentative.html]
+  expected: TIMEOUT

tests/wpt/meta/html/browsers/windows/document-domain-nested-navigate.window.js.ini

@@ -0,0 +1,3 @@
+[document-domain-nested-navigate.window.html]
+  [Navigated frame to about:blank and document.domain]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/embedded-opener.html.ini

@@ -0,0 +1,3 @@
+[embedded-opener.html]
+  [opener and embedded documents; using window.open()]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/nested-browsing-contexts/frameElement.sub.html.ini

@@ -0,0 +1,3 @@
+[frameElement.sub.html]
+  [The window's frameElement attribute must return its container element if it is a nested browsing context]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/nested-browsing-contexts/name-attribute.window.js.ini

@@ -0,0 +1,55 @@
+[name-attribute.window.html]
+  expected: TIMEOUT
+  [same-origin <frame>]
+    expected: TIMEOUT
+
+  [cross-origin <frame>]
+    expected: TIMEOUT
+
+  [same-origin <frame name=>]
+    expected: TIMEOUT
+
+  [cross-origin <frame name=>]
+    expected: TIMEOUT
+
+  [same-origin <frame name=initialvalue>]
+    expected: TIMEOUT
+
+  [cross-origin <frame name=initialvalue>]
+    expected: TIMEOUT
+
+  [same-origin <object>]
+    expected: TIMEOUT
+
+  [cross-origin <object>]
+    expected: TIMEOUT
+
+  [same-origin <object name=>]
+    expected: TIMEOUT
+
+  [cross-origin <object name=>]
+    expected: TIMEOUT
+
+  [same-origin <object name=initialvalue>]
+    expected: TIMEOUT
+
+  [cross-origin <object name=initialvalue>]
+    expected: TIMEOUT
+
+  [same-origin <embed>]
+    expected: TIMEOUT
+
+  [cross-origin <embed>]
+    expected: TIMEOUT
+
+  [same-origin <embed name=>]
+    expected: TIMEOUT
+
+  [cross-origin <embed name=>]
+    expected: TIMEOUT
+
+  [same-origin <embed name=initialvalue>]
+    expected: TIMEOUT
+
+  [cross-origin <embed name=initialvalue>]
+    expected: TIMEOUT

tests/wpt/meta/html/browsers/windows/noreferrer-window-name.html.ini

@@ -0,0 +1,7 @@
+[noreferrer-window-name.html]
+  expected: TIMEOUT
+  [Following a noreferrer link with a named target should not cause creation of a window that can be targeted by another noreferrer link with the same named target]
+    expected: TIMEOUT
+
+  [Targeting a rel=noreferrer link at an existing named window should work]
+    expected: FAIL

tests/wpt/meta/html/browsers/windows/targeting-cross-origin-nested-browsing-contexts.html.ini

@@ -0,0 +1,4 @@
+[targeting-cross-origin-nested-browsing-contexts.html]
+  expected: TIMEOUT
+  [Targeting nested browsing contexts]
+    expected: TIMEOUT