* [D] [Issue #27226] Multiple reparse point fixes:
- When a reparse point could not be persisted to disk, there was a chance of memory corruption.
- Renaming a directory that contained one or more reparse points under it, or in its sub-directories, would cause those reparse
points to get lost.
- Opening a reparse point directly and querying for information about that reparse point would not return reparse-based information
if Fast I/O was enabled (i.e. it would look like a regular file). This led to some strange behavior, such as when copying a reparse
point a 0 byte file would be created.