The test does not require the list of flows to be updated, to a single
cached version will do fine (this call otherwise would take ~40
seconds).

Downloading a run takes a non-significant amount of time (est. 300ms on
my current setup). It is unnecessary to compare against all >=100 runs,
while a handful should do fine (perhaps even just one should do).

The batch size required in some pages over 40 pages to be loaded, which
increased the workload unnecessarily. These changing preserve pagination
tests while lowering the amount of round trips required.

Since it is already covered by test_run_and_upload_randomsearch.

Speeds up ~25x, and reduces network traffic.

Loading a page takes ~600ms. I don't think testing with 3 pages is any
worse than 10. I also think this is an ideal candidate of test that
could be split up into (1) testing the url is generated correctly, (2)
testing a pre-cached result is parsed correctly and (3) testing the url
gives the expected response (the actual integration test).

If the test is that swapped parameters work, we don't need a complicated pipeline or dataset.

Some tests support both, by checking e.g. only a few runs vs all runs.

To cover for the skipping of test_get_run_trace