Add component extension whitelist to list of approved use cases

Bug: 1018108
Change-Id: I08fc6b7bb5247fdc0cf2eb36abc88867c1b564c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883510
Commit-Queue: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712068}

build/OWNERS.setnoparent

@@ -27,7 +27,8 @@ file://base/metrics/OWNERS
 # expose to the open web.
 file://third_party/blink/API_OWNERS
 
-# Extension API related files.
+# Extension related files.
+file://chrome/browser/extensions/component_extensions_whitelist/EXTENSION_WHITELIST_OWNERS
 file://extensions/common/api/API_OWNERS
 
 # This restriction is in place to avoid accidential addition to our top level

chrome/browser/extensions/component_extensions_whitelist/EXTENSION_WHITELIST_OWNERS

+# For Component Extensions
+rdevlin.cronin@chromium.org
+
+# For Component Apps
+benwells@chromium.org

chrome/browser/extensions/component_extensions_whitelist/OWNERS

@@ -2,11 +2,7 @@
 # Lead. See comment in whitelist.h
 set noparent
 
-# For Component Extensions
-rdevlin.cronin@chromium.org
-
-# For Component Apps
-benwells@chromium.org
+file://chrome/browser/extensions/component_extensions_whitelist/EXTENSION_WHITELIST_OWNERS
 
 # TEAM: extensions-dev@chromium.org
 # COMPONENT: Platform>Extensions