Add detail about L3 initialization

Bug: b/70299597
Merge of http://go/wvgerrit/67304
Test: Android, CE CDM, and Linux tests

There's a few different things that can go wrong in the L3
initialization, with seeding and device key failures among others. They
should be recorded in metrics to track. Along the same lines, since
multiple errors can happen in conjunction, metrics needs to change to
add more fields for errors. This CL also adds the
hidl_metrics_adapter_unittest to the Android test scripts.

Change-Id: Ie5bcf81bbe294a1136c58410f90087a13b3d911d

libwvdrmengine/cdm/metrics/src/metrics.proto

@@ -168,7 +168,7 @@ message WvCdmMetrics {
 
   // These are metrics recorded at the Engine level. This includes CryptoSession
   // metrics that were captured in the context of the engine.
-  // next id: 29
+  // next id: 31
   message EngineMetrics {
     optional CryptoMetrics crypto_metrics = 1;
 
@@ -200,6 +200,9 @@ message WvCdmMetrics {
     repeated CounterMetric cdm_engine_remove_usage_info = 26;
     repeated DistributionMetric cdm_engine_restore_key_time_us = 27;
     repeated CounterMetric cdm_engine_unprovision = 28;
+    // OEMCrypto Initialize Metrics.
+    optional ValueMetric level3_oemcrypto_initialization_error = 29;
+    optional ValueMetric previous_oemcrypto_initialization_failure = 30;
   }
 
   optional EngineMetrics engine_metrics = 1;