Test error: simulatenous resets resulted in 404

While testing #792, I ran into a random test failure in the ResetPojectRaceCondition.SimultaneousResetsDontResultIn404s method. I can't reproduce it consistently (I've run that test a dozen times since then with no 404s), so I isolated the test logs from the single failure in the hope that they might be useful in chasing down the cause of the 404. Here's the logs from skaffold during that test run, about 950 lines long:

test-with-404s.log

For contrast, here's the skaffold logs for a run that did NOT result in 404s (about 2870 lines, so it's possible I left out too much while isolating the earlier test failure):

test-no-404s.log

Hopefully this will end up proving useful in tracking down the error. Note that this was in local development, under Docker Desktop, so NFS was not involved in this 404.

Start with the ResetPojectRaceCondition.SimultaneousResetsDontResultIn404s test and compare the attached test-with-404s.log and test-no-404s.log Skaffold output. Re-run the test and trace the reset sequence until the intermittent 404 is explained; done means the race is addressed and the test no longer fails intermittently.