Similarly as #34472 already did for key-path spends, this PR adds a benchmark for P2TR script-path spends. So far we don’t have a benchmark on master yet that exercises the verification of taproot commitments (VerifyTaprootCommitment).
Note that the tapscript leaf intentionally includes a single OP_CHECKSIG as it likely reflects the real world best. Spending tapscript leafs without any signature checks don’t make much sense (they could be trivially tampered with and thus stolen by miners), and doing more than one signature check seems the exception rather than the rule.
The primary motivation for this PR is to evaluate how potential secp256k1 changes in pubkey tweaking (e.g. #1843) may impact script verification performance.