* More proper workaround for direct connection using Netty 4.2
* Add check for outdated Velocity
* BungeeCord support for Netty 4.2
* Use pooled allocator
* Small cleanup: only one allocator system property check, pin comment to static commit
* Set allocator type on Standalone using netty system property
* Don't mess with allocator, both BungeeCord and Velocity set it globally
* Temporarily remove io_uring support
In order to support io_uring transport after the 4.2 update, we'd need to separately handle 4.1 and 4.2 event loop group creation
* Add compileOnly netty io_uring dependency for Geyser-BungeeCord
* Exclude old incubator io_uring dependency on geyser-standalone
---------
Co-authored-by: Camotoy <20743703+Camotoy@users.noreply.github.com>
* Add run tasks and remove useless variables
The benefit of run tasks is that proxies like velocity can be prototyped on without using standalone or a GUI. Thus simplifying the prototyping/fixing process.
* Drop runwaterfall
