[wpt] Don't check resource timing for testharness*.js
If the renderer process running status-codes-create-entry.html ran
another testharness.js test before, the testharness scripts may be
cached 0 and spuriously fail the assertion that their resource timing
entries have positive duration.
Ignore these scripts, since the status-code.py?status=200 case
provides the same coverage.
Bug: None
Change-Id: I3a37c69f7511727be9c9be2f943f090264736d79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5893318
Commit-Queue: Noam Rosenthal nrosenthal@chromium.org
Reviewed-by: Noam Rosenthal nrosenthal@chromium.org
Commit-Queue: Jonathan Lee jonathanjlee@google.com
Cr-Commit-Position: refs/heads/main@{#1361388}