[7.7.0] Invalidate subtrees when a directory is deleted

[bazel-io]

FileSystemValueCheckerInferringAncestors claims that it is resilient to diffs which only report the root of a deleted subtree, but this wasn't true. Stale FileStateValues and DirectoryListingStateValues could linger around after moving an entire directory tree out of the workspace watched with --watchfs.

This is fixed by invalidating all FSVs and DLSVs under any deleted directory. Since these values and their keys do not depend on their parents, this requires a manual walk of the entire graph, making use of a prefix-free sorted map to speed up lookups per key.

Fixes #26863
Fixes #26866

Closes #26920.

PiperOrigin-RevId: 812740160
Change-Id: Id55329b5ffd3cf3e109ec102e86b6fb46335531b

Commit 8df327a

[iancha1992]

@lberki Could you please take a look at the presubmit failures? Thanks!

[fmeum]

@iancha1992 Could you apply this diff?

--- a/src/main/java/com/google/devtools/build/lib/skyframe/FileSystemValueCheckerInferringAncestors.java
+++ b/src/main/java/com/google/devtools/build/lib/skyframe/FileSystemValueCheckerInferringAncestors.java
@@ -341,7 +341,7 @@ public final class FileSystemValueCheckerInferringAncestors {
     boolean typeChanged = newFsv.getType() != oldFsv.getType();
     if (typeChanged) {
       parentListingKey(path).ifPresent(valuesToInvalidate::add);
-      if (oldFsv.isDirectory() && !newFsv.exists()) {
+      if (oldFsv.getType().isDirectory() && !newFsv.getType().exists()) {
         deletedDirectories.add(path);
       }
     }