Raise FileNotFoundError in WindowsFileLock
Hi ! Could you clarify what it fixes exactly and give more details please ? Especially why this is related to the windows hanging error ? This has already been merged, but I'll clarify the idea of this PR. Before this merge, FileLock was the only component affected by the max path limit on Windows (that came to my notice) because of its infinite loop that would suppress errors. So instead of suppressing the `FileNotFoundError` that is thrown by `os.open` if the file name is longer than the max allowed path length, this PR reraises it to notify the user.
Closes #2443 