test: skip tx_stats_bench 10 TPS sub-test on merge-train/fairies

[vezenovm]

Motivation

Cherry-pick of #23092 onto merge-train/fairies. The same verifies transactions at 10 TPS flake in tx_stats_bench.test.ts:268 that #23092 skips on merge-train/spartan is now blocking PRs based on merge-train/fairies (e.g. seen on the mv/f-637-public-self-creator branch in ci-full):

● transaction benchmarks › verifies transactions at 10 TPS
  expect(received).toBe(expected) // Object.is equality
  Expected: true
  Received: false
    at toBe (bench/tx_stats_bench.test.ts:268:69)

#23092 has the full analysis: under 8x parallel IVC verifications (each spawning a bb subprocess via the bb.js NativeUnixSocket backend introduced in #21564), at least one verification intermittently returns valid:false. None of the merge-train commits triggering the failure touch the bb-prover IVC verifier path.

Notes

• Re-enable it.skip → it once the bb.js backend's concurrent-verifier interaction (withVerifierInstance lifecycle) is hardened.

[vezenovm]

This unblocks #23062 and ci-full on merge-train/fairies more generally. We can also wait for merge-train/spartan to be fixed up. But then we have to wait for that to be synced into next so we can updates the fairies branch. What do you think @nchamo?

[nchamo]

Let's not do this now, and see how we can apply the same fix they apply. Otherwise, we would be turning off their test when this is merged to next

[vezenovm]

Closing, we will wait for merge-train/spartan to resolve the test