Some cypress tests affect the state of versions and tasks that are used again in subsequent tests. We should identify these tests and make them atomic so we can consider parallelizing our cypress tests.
version/task_filters.ts may rely on tests that restart a version. I can tell because the statuses in the in status selector dropdown differ from when the version/task_filter test runs in sequence vs solo.
version/version_route.ts expects a task status to transition to will-run from succeess before it is ran