Refactor transport IO with System.IO.Pipelines

Introduces `System.IO.Pipelines` for efficient byte movement, replacing direct `System.Threading.Channels` interactions in the core transport logic. This change streamlines buffer management, improves performance, and forms a key part of separating the transport layer.

- Migrates `ClientByteMover` to a `Pipe`-centric architecture, utilizing `IoBuffer` for `MemoryPool` integration.
- Updates `ClientState` to internally manage `Pipe` instances.
- Adjusts `ConnectionHandle` and `NetworkBuffer` to interoperate with the new `IoBuffer` and `Pipe` paradigm.
- Increases default HTTP/2 stream window size and max frame size, and HTTP/3 QPACK table capacity for improved performance.
- Removes `Servus.Akka` project reference from `TurboHTTP.csproj`.

Author: st0o0

src/Directory.Packages.props

@@ -8,9 +8,7 @@
     <PackageVersion Include="Akka.Streams.TestKit" Version="1.5.65" />
     <PackageVersion Include="Akka.TestKit.Xunit" Version="1.5.65" />
   </ItemGroup>
-  <ItemGroup Label="Servus">
-    <PackageVersion Include="Servus.Akka" Version="0.3.10" />
-  </ItemGroup>
+
   <ItemGroup Label="Testing">
     <PackageVersion Include="Microsoft.Testing.Extensions.CodeCoverage" Version="18.6.2" />
     <PackageVersion Include="xunit.v3.mtp-v2" Version="3.2.2" />