fix: correct mtime for useFsEventsOnParentDirectory events

[llllvvuu]

Fixes #57792

Problem

On macOS Sonoma, getModifiedTime(fileOrDirectory) will return the wrong mtime for file change events in FileSystemEntryKind.Directory watchers, since foo/bar.ts modification will not bump foo/ mtime nor will the event itself specify an mtime. This will cause file modifications to not be picked up when running tsc --watch --watchFile usefseventsonparentdirectory.

Solution

Change getModifiedTime(fileOrDirectory) to getModifiedTime(filename), where filename is calculated by passing through entryKind.

Testing

Provided regression test which fails on main. The macOS Sonoma behavior is modeled by the mock filesystem using a new option modifyFileWithoutModifyDirectory.

[llllvvuu]

@microsoft-github-policy-service agree

[sheetalkamat]

This isnt the right fix and #57938 addresses the issue instead.