Fix an oddity with COOP WPTs

Tests starting with unsafe-none are supposed to specify unsafe-none
explicitly in the headers. Tests starting with unspecified are meant
for testing not having a COOP header at all. Somehow only one
unsafe-none test has a header, that's fixed in this patch.

BUG=1318373

Change-Id: I5778b226194dba5c68d6e8ee837750276a29224c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3679999
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Hemery <ahemery@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1009477}
diff --git a/html/cross-origin-opener-policy/popup-unsafe-none-with-cross-origin.https.html.headers b/html/cross-origin-opener-policy/popup-unsafe-none-with-cross-origin.https.html.headers
new file mode 100644
index 0000000..073ce7a
--- /dev/null
+++ b/html/cross-origin-opener-policy/popup-unsafe-none-with-cross-origin.https.html.headers
@@ -0,0 +1 @@
+Cross-Origin-Opener-Policy: unsafe-none
diff --git a/html/cross-origin-opener-policy/popup-unsafe-none-with-same-site.https.html.headers b/html/cross-origin-opener-policy/popup-unsafe-none-with-same-site.https.html.headers
new file mode 100644
index 0000000..073ce7a
--- /dev/null
+++ b/html/cross-origin-opener-policy/popup-unsafe-none-with-same-site.https.html.headers
@@ -0,0 +1 @@
+Cross-Origin-Opener-Policy: unsafe-none