fix(esp-tls): Remove the legacy use_km_key option

components/esp-tls/esp_tls_mbedtls.c

@@ -639,7 +639,9 @@ static esp_err_t set_pki_context(esp_tls_t *tls, const esp_tls_pki_t *pki)
             esp_ecdsa_opaque_key_t opaque_key = {
                 .curve = curve,
                 .efuse_block = tls->ecdsa_efuse_blk,
-                .use_km_key = false,
+#if SOC_KEY_MANAGER_SUPPORTED
+                .key_recovery_info = NULL,
+#endif /* SOC_KEY_MANAGER_SUPPORTED */
             };
 
             // Import opaque key reference

docs/en/api-reference/peripherals/hmac.rst

@@ -183,7 +183,6 @@ Now we can calculate an HMAC for software usage with the saved key through the P
 
     // Create opaque key reference
     esp_hmac_opaque_key_t opaque_key = {
-        .use_km_key = false,
         .efuse_key_id = HMAC_KEY4,
     };
 

docs/zh_CN/api-reference/peripherals/hmac.rst

@@ -183,7 +183,6 @@ HMAC 的第三种应用场景是将其作为密钥，启用软禁用的 JTAG 接
 
     // 创建不透明密钥引用
     esp_hmac_opaque_key_t opaque_key = {
-        .use_km_key = false,
         .efuse_key_id = HMAC_KEY4,
     };