feat(server): support native Windows builds

[TalaatHarb]

Which issue does this PR address?

Closes #4037

Rationale

Provide the ability to build the system natively on windows os

What changed?

iggy-server could not be built or run natively on Windows. The failure was not a
single blocker but a chain of them: build/runtime dependency issues and also Unix only syscalls in the storage and transport layers. This PR adds windows alternative for the Unix only syscalls and adds documentation of how to build iggy-server on windows.

Local Execution

• Passed on Windows
• Pre-commit hooks that have windows setup ran. (helmfmt for example isn't available through winget so I didn't run it)
  due to the nature of this PR focusing on windows setup the behavior of the pre-commit hooks might not cover everything

AI Usage

Tools used: GitHub Copilo was used
Sope of usage: generated functions as alternatives for the Unix only issues
Verification: Build, Tests and basic runtime behavior verified after the modifications (This PR makes cargo build -p server --bin iggy-server produce a working Windows binary that boots, serves traffic, shuts down gracefully, and recovers
its data on restart which wasn't available before). Other OS targets behavior should be intact and verified through CI.
I can explain the logic behind every line of the code if asked.

[github-actions]

Thanks for the PR. It is labeled S-waiting-on-review and queued for review.

Slash commands (own line, regular comment) move it around the queue:

• /ready - back to S-waiting-on-review after addressing feedback
• /author - flip to S-waiting-on-author while you finish changes
• /request-review @user-or-team - request a reviewer

See CONTRIBUTING.md for details.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.53%. Comparing base (40be168) to head (f457e62).
⚠️ Report is 57 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #4050      +/-   ##
============================================
+ Coverage     85.40%   85.53%   +0.12%     
  Complexity     1402     1402              
============================================
  Files          1240     1240              
  Lines        186294   186213      -81     
  Branches     152600   152518      -82     
============================================
+ Hits         159109   159279     +170     
+ Misses        23132    22890     -242     
+ Partials       4053     4044       -9     

Components	Coverage Δ
Rust Core	86.47% <ø> (+0.01%)	⬆️
Java SDK	67.29% <ø> (ø)
C# SDK	76.33% <ø> (-0.02%)	⬇️
Python SDK	90.06% <ø> (ø)
PHP SDK	85.65% <ø> (ø)
Node SDK	96.24% <ø> (+1.76%)	⬆️
Go SDK	69.35% <ø> (+0.03%)	⬆️

Files with missing lines	Coverage Δ
core/journal/src/file_storage.rs	75.72% <ø> (ø)
core/journal/src/prepare_journal.rs	92.85% <ø> (+0.54%)	⬆️
core/journal/src/superblock.rs	93.73% <ø> (+0.53%)	⬆️
core/message_bus/src/fd_transfer.rs	97.05% <ø> (+8.34%)	⬆️
core/message_bus/src/installer/mod.rs	92.30% <ø> (-0.92%)	⬇️
core/message_bus/src/socket_opts.rs	93.33% <ø> (+2.02%)	⬆️
core/message_bus/src/transports/tcp.rs	98.95% <ø> (+0.31%)	⬆️
core/metadata/src/impls/metadata.rs	88.90% <ø> (+0.21%)	⬆️
core/partitions/src/offset_storage.rs	91.58% <ø> (+0.61%)	⬆️
core/server/src/main.rs	66.66% <ø> (ø)
... and 4 more

... and 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hubcio]

looks like clippy is failing. please fix :) after that we can check.

[hubcio]

/author

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

If you need a review, please ensure CI is green and the PR is rebased on the latest master. Don't hesitate to ping the maintainers - either @core on Discord or by mentioning them directly here on the PR.

Thank you for your contribution!