When accessing triage from the individual test view, the "Search for bug" is incorrect

[schenney-chromium]

To reproduce:

• Find a failing test and go to the individual test view, where youhave the test name and then a box for each browser with PASS/FAIL, "Compare" etc. e.g. https://wpt.fyi/results/css/css-transforms/2d-rotate-001.html?label=master&label=experimental&aligned
• Go into Triage mode and click on the "FAIL" for a browser to add it to the triage set. Note it's not obvipous that you need to click on "FAIL". Clicking on "Compare" accesses compare, rather than adding for triage.
• Click TRIAGE and note that the "Search for bug" link is searching for "Harness status" and not the test name.

[stephenmcgruer]

(Likely related to https://github.com/web-platform-tests/wpt.fyi/issues/2286)

[foolip]

I've seen something similar when triaging testharness.js subtests. Then, searching searches for the name of the subtest, which honestly is very unlikely to find a bug, and just searching by the test name is more likely to find something. https://github.com/web-platform-tests/wpt.fyi/issues/2286 is about the harness status being treated as a subtest name when writing out the metadata, but here the issue is considering subtest names at all.