Description:
Allow the verified access APIs (https://support.google.com/chrome/a/answer/7156268) to be accessible from kiosk mode

Use case:
Currently the verified access api is only accessible from extensions running within a user session.  However, if the chromebook is running in kiosk mode, there isn't a way to ensure that the device is trusted.  By opening this API to kiosk apps, enterprises will able to assert that their kiosks are trusted and allow some level of elevated access to them.

Motivation:
If an enterprise has an internal kiosk set up for user registration, or that can perform any sort of sensitive action/access sensitive data, they likely want to ensure that the requests are coming from a trusted device (possibly in addition to user authentication).  The verified access would allow them to authenticate the kiosk device and assert that the device is enrolled in their enterprise, is not in developer mode, etc.  Coupled with user authentication, this can then be used to verify that the kiosk's requests are coming from a trusted source.

Existing workarounds:
From a user session, use the verified access api/extension to request a device-wide certificate, which IIRC would be presented even in kiosk mode, but this forces the enterprise to allow issuing device-wide certificates, which may be unacceptable as per their policies.