Fix Redaction Logic to Use Notarized Transcript

[heeckhau]

When implementing the getSecretResponse function to redact the response in a browser extension plugin, the current implementation performs a regular web request replay (without TLSNotary) and uses the result for redactions. However, this replayed response is not always identical to the original notarized response, leading to incorrect or inaccurate redactions.

To resolve this issue, we need to ensure that the actual notarized transcript, which the Prover has in plaintext, is used for redactions instead of relying on the result of a replayed request.