Logging CDM session ID on Decrypt() failures.

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

This changes extends the CryptoSession logging to include the OEMCrypto
session ID in its decrypt failure logs, and adds a new CdmSession
decrypt failure log which includes the CDM session ID.  The CDM session
directly maps to the MediaDRM session ID, making app debugging easier.

The Decrypt() code pathway is one of the most frequently called
portions of the CDM code, and the pathway attempts to make as few
logging calls as possible in order to keep latency low and log
verbosity to a minimum.  It is anticiapted that when a call to
Decrypt() fails, there will be a burst of failures as the app may
make several calls to Decrypt() before handling the first decrypt
error.

To keep logging low, the following rules are followed:
- CryptoSession: decrypt errors are only logged when the decrypt error
  changes.
- CdmSession: decrypt errors are only logged when the last call to
  decrypt had succeeded.

Bug: 183984396
Test: MediaGTS with decrypt failures
Change-Id: Ic6124646d129efbc8a690b5bfd4dc422e04e677b

libwvdrmengine/cdm/core/src/crypto_session.cpp

@@ -1823,7 +1823,12 @@ CdmResponseType CryptoSession::Decrypt(
           "oec_session_id = %u",
           oec_session_id_);
     } else {
-      LOGE("OEMCrypto_DecryptCENC failed: status = %d", static_cast<int>(sts));
+      LOGE(
+          "OEMCrypto_DecryptCENC failed: oec_session_id = %u, "
+          "security_level = %s, status = %d",
+          oec_session_id_,
+          RequestedSecurityLevelToString(requested_security_level_),
+          static_cast<int>(sts));
     }
   }