Reconsider removing "potentially deleted" tests once using new test tracking by default #5739
Description
There were two different issues reported in #5734:
- The test markers for tests that aren't run disappear
- The test markers come back when modifying the file
I'm using that issue to track the second, but this is to track the first. It's actually by-design as the code currently is. Without the new tracking, we don't know if the test was not in the results because a) you stopped running early (or used @soloTest) or b) you had deleted the test.
However, with the new test tracking, we could perhaps remove the functionality of deleting "potentially deleted" nodes and instead just rely on the tracking to handle it (remove the node when the tracked position goes away).
It will be easier to do this when we're just using the new tracking by default, so bumping this until then,