Add security class keystore2_key.

Keystore 2.0 has a different set of permission that it enforces.
We introduce keystore2_key so that we can set up policy for both
Keystore 1.0 and Keystore 2.0 for a gradual transition from one to
the other.

Bug: 158500146
Test: None
Change-Id: I3dcab06d73d242d63d21883659c304dfab8bf74f

private/access_vectors

@@ -711,6 +711,31 @@ class keystore_key
 	gen_unique_id
 }
 
+class keystore2
+{
+	add_auth
+	clear_ns
+	get_state
+	lock
+	reset
+	unlock
+}
+
+class keystore2_key
+{
+	delete
+	gen_unique_id
+	get_info
+	grant
+	list
+	manage_blob
+	rebind
+	req_forced_op
+	update
+	use
+	use_dev_id
+}
+
 class drmservice {
 	consumeRights
 	setPlaybackStatus

private/security_classes

@@ -153,8 +153,14 @@ class service_manager           # userspace
 # hardware service manager      # userspace
 class hwservice_manager
 
-# Keystore Key
+# Legacy Keystore key permissions
 class keystore_key              # userspace
 
+# Keystore 2.0 permissions
+class keystore2                 # userspace
+
+# Keystore 2.0 key permissions
+class keystore2_key             # userspace
+
 class drmservice                # userspace
 # FLASK