Implement Infrastructure for AR and VR permissions

This change begins implementing the infrastructure for AR and VR
permissions so that WebXr can switch to using Permissions instead of a
custom consent flow.  Note that neither permission is intended to be
exposed to blink at this time, and neither permission is expected to
be called, therefore all calls to these permissions are currently
blocked while development is occurring.

Bug: 1033592
Change-Id: Ia51f9df7f66c42d2b5fad17ef9e9206b7bedd799
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965974
Commit-Queue: Alexander Cooper <[email protected]>
Reviewed-by: Tommy Li <[email protected]>
Reviewed-by: Steven Holte <[email protected]>
Reviewed-by: Balazs Engedy <[email protected]>
Reviewed-by: Alex Moshchuk <[email protected]>
Reviewed-by: Bo <[email protected]>
Reviewed-by: Finnur Thorarinsson <[email protected]>
Reviewed-by: Mounir Lamouri <[email protected]>
Cr-Commit-Position: refs/heads/master@{#726239}
diff --git a/chrome/browser/permissions/permission_request.h b/chrome/browser/permissions/permission_request.h
index 974dd8c0..6e4db4a 100644
--- a/chrome/browser/permissions/permission_request.h
+++ b/chrome/browser/permissions/permission_request.h
@@ -48,6 +48,8 @@
   PERMISSION_PAYMENT_HANDLER = 18,
   PERMISSION_NFC = 19,
   PERMISSION_CLIPBOARD_READ_WRITE = 20,
+  PERMISSION_VR = 21,
+  PERMISSION_AR = 22,
   // NUM must be the last value in the enum.
   NUM
 };