chore(debug): per-request gen-mode result dumps

The asymmetric and symmetric result dumps wrote a single fixed
filename (teesim-gen-mode-asym.bin / -sym.bin), so each forge
overwrote the previous one and only the final reply survived a
capture -- which is why a tester's zip showed one app's good chain
while the failing chain was already gone.

Tag both dumps with uid and tx, matching the request dumps, so every
forged chain is retained and correlatable with its request.

app/src/main/java/org/matrix/TEESimulator/interception/keystore/shim/KeyMintSecurityLevelInterceptor.kt

@@ -865,7 +865,10 @@ class KeyMintSecurityLevelInterceptor(
                 )
             }
 
-            return InterceptorUtils.createTypedObjectReply(metadata, diagnosticTag = "gen-mode-sym")
+            return InterceptorUtils.createTypedObjectReply(
+                metadata,
+                diagnosticTag = "gen-mode-sym-uid$callingUid-tx$txId",
+            )
         }
 
         // The framework can designate the attest key by alias OR — for a persistent key the caller
@@ -978,7 +981,7 @@ class KeyMintSecurityLevelInterceptor(
 
         return InterceptorUtils.createTypedObjectReply(
             response.metadata,
-            diagnosticTag = "gen-mode-asym",
+            diagnosticTag = "gen-mode-asym-uid$callingUid-tx$txId",
         )
     }