Accept a security level to be specified during provisioning

[ Merge of http://go/wvgerrit/98694 and http://go/ag/11052323 ]

In earlier releases, provisioning would occur based on a cached
security level. If an open session call returned a NotProvisionedException
the security level would be cached for use with any future provisioning
call.

An app would have to set the security level, then call openSession,
have it fail and then request provisioning. This fits the normal flow of
most apps. Still on occasion, an app might change requested security level
after an openSession call failed. Using the cached security level
would result in unexpected behavior.

This change allows provisioning to occur at the last security level that
was set.

Bug: 129356527
Test: wv unit/integration tests, GTS tests (GtsMediaTestCases)
Change-Id: I8d9234eec2b23a9c913e77a709943b431e25e43e

libwvdrmengine/cdm/test/wv_cdm_metrics_test.cpp

@@ -58,7 +58,8 @@ TEST_F(WvContentDecryptionModuleMetricsTest, EngineOnlyMetrics) {
   EXPECT_EQ(wvcdm::NO_ERROR,
             decryptor_.GetProvisioningRequest(
                 cert_type, cert_authority, kDefaultCdmIdentifier,
-                kEmptyServiceCertificate, &request, &provisioning_server_url));
+                kEmptyServiceCertificate, kLevelDefault, &request,
+                &provisioning_server_url));
 
   drm_metrics::WvCdmMetrics metrics;
   ASSERT_EQ(wvcdm::NO_ERROR,