gh-85470: Delay load ole32.dll in the _ctypes module

[serhiy-storchaka]

Measured on Windows 11 with a debug x64 build -- import _ctypes before the change loads user32.dll, ole32.dll, gdi32.dll, win32u.dll and combase.dll; after it, only combase.dll remains (pulled in by oleaut32, which does not depend on user32). A plain python.exe already loaded none of them, so ctypes was the last thing making the interpreter a GUI process -- and it is the module a console script needs in order to call SetConsoleCtrlHandler() in the first place.

ProgIDFromCLSID() in SetComError() is the only ole32 use in _ctypes, and it is reached only when formatting an error from a COM interface method. PCbuild/_wmi.vcxproj already delay loads the same DLL.

test_ctypes passes (679 tests). This covers the PCbuild build only; resolving ProgIDFromCLSID() through GetProcAddress() would also cover other toolchains, at the cost of some C code.

• Issue: [ctypes] Enable handling logoff and shutdown Windows console events #85470

[serhiy-storchaka]

Verified the actual effect, not just the module list: two processes started from the same build in the same interactive session, one of them force-loading user32.dll to emulate the previous state, each with a SetConsoleCtrlHandler() installed through ctypes. On logoff the process without user32.dll received CTRL_LOGOFF_EVENT and ran its handler; the one with user32.dll loaded was terminated without any event.