Revise usage entry metadata

[ Merge of http://go/wvgerrit/23742 ]

In OEMCrypto V13, usage table header and usage entries are stored in
persistent non-secure storage and loaded and unloaded from the TEE.
Information needs to be maintained to assist finding the associated license
or usage information. This information has been revised for usage information
to use key set id and usage info file name rather than provider session
token and app id.

The app id is stored in a hashed form (usage info file name) and was not
extractable during the upgrade process to OEMCrypto V13. Due to this
DeviceFiles UsageInfo routines have switched to use usage info file name
rather than app id as a key.

b/34327459

Test: Verified by unit/integration tests on angler
Change-Id: I95aa0435d0955c61fc45b951f5b5d44de2ba5cfc

libwvdrmengine/cdm/core/src/device_files.proto

@@ -74,12 +74,12 @@ message UsageTableInfo {
     enum UsageEntryStorage {
       LICENSE = 1;
       USAGE_INFO = 2;
+      UNKNOWN = 3;
     }
 
     optional UsageEntryStorage storage = 1;
-    optional bytes key_set_id = 2;  // used if storage is LICENSE
-    optional bytes provider_session_token = 3;  // used if storage is USAGE_INFO
-    optional bytes app_id = 4; // used if storage is USAGE_INFO
+    optional bytes key_set_id = 2;
+    optional bytes usage_info_file_name = 3; // hash of the app_id
   }
 
   optional bytes usage_table_header = 1;