fix(harness): add fixes for browser benches

[themighty1]

This PR fixes problems related to running browser benches reliably.

• restart RPC server periodically to avoid OOM (see explanation below)
• disables registering a tracing subscriber in the wasm build
• increase timeout for long running benches
• dont log a non-critical chrome debug protocol error

Depends on: #945

Memory leak

The memory leak can be seen on the below screenshots taken a few minutes apart. The memory grows until 4GB and then an oom panic happens. Chrome memory profiling tools suggested that at the time of the panic, 4GB of memory was retained by wasm-bindgen's CLOSURE_DTORS.

[themighty1]

Some of the issues raised here were addressed in separate PRs.
For the remaining issues I opened a fresh PR to keep things clean #962