test(strategy): stop the fail-fast fetch test depending on a fast machine

The test gave the first fetch a 1s budget, which a loaded machine can spend before git even connects, so the remote saw no connection and the test failed. It now allows 5s, waits for the server to count the connection, and requires the fail-fast fetch to beat the budget rather than a fixed 500ms.