[File Locksmith] Fix Interop access-violation crashes from TerminateThread hang recovery

[Ryan Johnson (AMDphreak)]

Summary

• Remove the TerminateThread watchdog in NtdllExtensions::handles(). Killing a thread mid-NtQueryObject / CRT heap use causes later 0xc0000005 crashes in PowerToys.FileLocksmithLib.Interop.dll (WER offsets map to the worker lambda / memcpy).
• Skip handle access masks known to hang NtQueryObject/GetFileType (including the previously commented 0x0012019f filter).
• Null-check UNICODE_STRING buffers and OpenProcess in pid_to_full_path.

Fixes / relates to: #45158, #47200

This is distinct from the already-merged icon crash fix in #48719 (0xc000027b).

Test plan

• Build FileLocksmithLibInterop / File Locksmith UI (x64 Release)
• Right-click a file/folder → Unlock with File Locksmith repeatedly (10+ times) on a machine that previously crashed within ~5s
• Confirm no Application Error / c0000005 for PowerToys.FileLocksmithUI.exe in Event Viewer
• Confirm results still populate for a known locked file (e.g. open document)
• Optional: right-click a drive root (enumerates many handles) and verify UI stays up

Made with Cursor

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Dave Rayment (daverayment)]

Converted this to draft, as it's AI-developed and there is no proof given that this solves the underlying issue.

Ryan Johnson (@AMDphreak) Please fill in the PR details correctly, read the contributor guidelines and refer us to the issue where a maintainer agreed with your approach and approved your work on this. You also seem to have forgotten to include your test results. Many thanks.