test(chrome): compare a compound text selector across both matchers

one page, both resolvers, text written before and after the key beside
it. the object form now encodes its keys in the order the filters state
them rather than the order a map iterates, so both orders are asked.

the row and the badge under it share a class so the innermost rule has
something to drop, and {text, clickable} pins that text is anded before
that rule runs: the innermost element carrying "January" is the option,
and the select is the only element that is both.

internal/driver/chrome/testdata/selector-parity.html

@@ -15,7 +15,7 @@
     <div id="draft_row"><span id="draft_badge">Sent ✓</span></div>
     <div id="unsent_row"><span id="unsent_badge">3<!-- --> unsent</span></div>
     <div id="split_row">Sen<span id="split_tail">t here</span></div>
-    <div id="nested_row">Sent <span id="nested_badge">Sent</span></div>
+    <div id="nested_row" class="status">Sent <span id="nested_badge" class="status">Sent</span></div>
     <!-- secure is derived from the field type, so the fields here have to cover
          every state it answers with: the password entry, the three shapes of
          editable field that are not one, and a control that is no field at all