Replace ACE with native IO implementation

[0blu]

🍰 Pullrequest

This pr will replace ACE with a self-made but highly performant native solution.

The implementation was inspired by boost asio, meaning that everything is asynchronous and requires a callback.
Users have to guarantee the lifetime of the socket throughout the transaction (aka. use std::shared_ptr<>).

Since cMaNGOS and TrinityCore already switched to Boost and this native IO implementation is very similar to Boost, some similarities in the network code can be found and compared against.

Native system function are used. There are slightly different backend implementations on each OS:

• Windows IOCP
• Linux epoll (with the possibility to add io_uring support)
• macOS kqueue

Want to test it? 🧪

Just merge these two commits into your repo.
https://github.com/0blu/vmangos-core/tree/native-squash-merge-2024-11-17
As soon this native branched is squashed-merged with development you can easily rebase->drop->cherry-pick it with the new official commit.

Todo / Checklist

• Test on low pop server
• Test on medium pop server (3k-6k)
• Update build guide

[mserajnik]

@0blu

Build fails under Ubuntu/GCC with 8a78b31 when ENABLE_MAILSENDER is set:

/core/src/realmd/AuthSocket.cpp: In member function 'void AuthSocket::_HandleLogonProof__PostRecv(const std::shared_ptr<const sAuthLogonProof_C>&, const std::shared_ptr<const PINData>&)':
/core/src/realmd/AuthSocket.cpp:714:56: error: 'GetRemoteIpAddress' was not declared in this scope; did you mean 'GetRemoteIpString'?
  714 |                 mail->substitution("%originating_ip%", GetRemoteIpAddress());
      |                                                        ^~~~~~~~~~~~~~~~~~
      |                                                        GetRemoteIpString

Maybe it would be a good idea to enable all the optional features (like ENABLE_MAILSENDER) for the "test" workflows to catch stuff like this easier? Saw that that's implemented now (👍) and that the workflow currently fails with the same error.