When generating a stream clone, we spend a large amount of time auditing path.
Before this changes, the first run was warming the vfs cache for the other
runs, leading to a large runtime difference and a "faulty" reported timing for
the operation.

We now clear this important cache between run to get a more realistic timing.

Below are some example of median time change when clearing these cases. The
maximum time for a run did not changed significantly.

### data-env-vars.name             = mozilla-central-2018-08-01-zstd-sparse-revlog
  # benchmark.name                = hg.perf.exchange.stream.generate
  # bin-env-vars.hg.flavor         = default
  # bin-env-vars.hg.py-re2-module  = default
  # benchmark.variants.version    = latest
no-clearing:    17.289905
cache-clearing: 21.587965  (+24.86%, +4.30)
 ## data-env-vars.name             = mozilla-central-2024-03-22-zstd-sparse-revlog
no-clearing:    32.670748
cache-clearing: 40.467095  (+23.86%, +7.80)
 ## data-...