t/ithread.t is failing on Windows due to ithreads socket handling

[toddr-bot]

Description

The t/ithread.t test is currently skipped on Windows (MSWin32) because ithreads socket handling does not work correctly with Win32::Process.

This was discovered during work on #12 (detaching threads in ChildFunc). The test fails on Windows CI, so a skip was added as a workaround.

Expected behavior

The ithreads server test should pass on Windows, or there should be a documented alternative approach for Windows thread/process handling.

Context

• Related: t/ithreadm.t is failing on windows. #19 (t/ithreadm.t also failing on Windows)
• The skip was added in PR fix: Detach threads in ChildFunc to prevent memory leaks #22

Next steps

• Investigate whether Windows socket handling can be fixed for ithreads mode
• Consider if a different approach (e.g., non-blocking I/O or a Windows-specific code path) could make this work