Implement the private API for quick unlock.

chrome/common/extensions/permissions/chrome_api_permissions.cc

Index: chrome/common/extensions/permissions/chrome_api_permissions.cc
diff --git a/chrome/common/extensions/permissions/chrome_api_permissions.cc b/chrome/common/extensions/permissions/chrome_api_permissions.cc
index c4948140abe58da46d9f41c3a4c825b3617bee0e..1e9ca607d2a98ded8194f373a2488b273b8a36b0 100644
--- a/chrome/common/extensions/permissions/chrome_api_permissions.cc
+++ b/chrome/common/extensions/permissions/chrome_api_permissions.cc
@@ -199,6 +199,8 @@ std::vector<APIPermissionInfo*> ChromeAPIPermissions::GetAllPermissions()
        APIPermissionInfo::kFlagCannotBeOptional},
       {APIPermission::kResourcesPrivate, "resourcesPrivate",
        APIPermissionInfo::kFlagCannotBeOptional},
+      {APIPermission::kQuickUnlockPrivate, "quickUnlockPrivate",
+       APIPermissionInfo::kFlagCannotBeOptional},

[Devlin, 2016/05/31 22:58:38]

Why can't it be optional?

[jdufault, 2016/06/01 00:07:36]

Changed to kFlagNone. I don't have a strong opinion here, but every consumer
needs the permission to perform any functionality w.r.t. quick unlock, so it
doesn't make sense for it to be optional.

[Devlin, 2016/06/01 17:44:12]

Well, it does in the case of an app/extension that does more than just quick
unlock.  CannotBeOptional should be used rarely, because optional permissions
are far preferable if it's feasible.  The extension can always make the choice
to still have it be a required permission if it's core to its functionality. 
(Of course, not as big a deal here, since it's a private API.)

 
       // Full url access permissions.
       {APIPermission::kDebugger, "debugger",