root: add CRYPTO_OWNERS

Per discussion on chrome-security-leads@, this change centralizes
ownership of cryptographic code in chromium within a single root-level
file. Existing OWNERS files for crypto code are left in place (since
they reflect expertise within specific directories) but //CRYPTO_OWNERS
is added as a fallback owner to all of them.

Bug: None
Change-Id: I069f3c9085219f78504f533e84046aadb01fa11d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5770906
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Reviewed-by: Andrew Whalley <awhalley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1341684}

CRYPTO_OWNERS

@@ -0,0 +1,13 @@
+# People listed in this file are responsible for making decisions about
+# cryptography use in Chromium. If you are adding new cryptographic code, or
+# adding complex uses of existing cryptographic code, please consult one of
+# these people.
+
+agl@chromium.org
+bbe@chromium.org
+davidben@chromium.org
+ellyjones@chromium.org
+estark@chromium.org
+mattm@chromium.org
+svaldez@chromium.org
+tsepez@chromium.org

components/encrypted_messages/OWNERS

@@ -1 +1,3 @@
 estark@chromium.org
+
+file://CRYPTO_OWNERS

components/webcrypto/OWNERS

@@ -1,3 +1,5 @@
 davidben@chromium.org
 ellyjones@chromium.org
 tsepez@chromium.org
+
+file://CRYPTO_OWNERS

crypto/OWNERS

@@ -2,3 +2,5 @@ set noparent
 agl@chromium.org
 davidben@chromium.org
 mattm@chromium.org
+
+file://CRYPTO_OWNERS

third_party/boringssl/OWNERS

@@ -2,3 +2,5 @@ agl@chromium.org
 bbe@chromium.org
 davidben@chromium.org
 svaldez@chromium.org
+
+file://CRYPTO_OWNERS