Fix kernel capture when the driver directory is missing

[DesolateVE]

Enabling kernel capture fails on systems where %SystemRoot%\System32\driver does not exist. DebugView++ registers dbgvpp.sys at that location, but extraction does not create the parent directory. The Service Control Manager reports error 7000 (the system cannot find the path specified), followed by the UI error "Could not find the kernel messages driver device name".

Create the driver's parent directory before extracting the embedded resource. Directory creation is idempotent, skips an empty parent path, and reports filesystem errors to the internal log before returning from extraction. The existing driver location is preserved.

Validation:

• Built the Debugviewpp Release x64 target successfully with Visual Studio 2026 Build Tools.
• git diff --check passed.
• Before this change, manually creating C:\Windows\System32\driver resolved kernel capture on the affected system. Runtime testing of the patched executable has not yet been performed.

Maintainer question: Is the singular System32\driver directory intentional to keep the capture driver separate, or should the location be the standard System32\drivers directory? This fix preserves the current location pending clarification.