Cl binary nio channel

[clementleclercRTE]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

Fixes #3881

What kind of change does this PR introduce?

Migrates the binary reader and writer from DataInputStream/DataOutputStream over
BufferedInputStream/BufferedOutputStream to direct ByteBuffer + java.nio.channels.ReadableByteChannel/WritableByteChannel.

What is the current behavior?

• BinReader wraps the caller's InputStream into a BufferedInputStream + DataInputStream.
• BinWriter wraps the caller's OutputStream into a BufferedOutputStream + DataOutputStream.
• NetworkSerDe.copy() uses PipedInputStream/PipedOutputStream.
• When the underlying source is a Files.newInputStream(path) / Files.newOutputStream(path) (themselves wrapping a FileChannel), the data path goes Channel → Stream → DataStream, with
  redundant adapters.

What is the new behavior (if this is a feature change)?

• BinReader now reads through a BufferedChannelReader backed by a direct ByteBuffer and a ReadableByteChannel.
  • BinWriter now stages body bytes in a direct ByteBuffer (GrowingByteBuffer) and drains them straight to a WritableByteChannel on close.
  • New public constructors BinReader(ReadableByteChannel, byte[]) / BinReader(Path, byte[]) and BinWriter(WritableByteChannel, byte[], String) / BinWriter(Path, byte[], String) avoid the
    Channel → Stream → Channel double-wrapping when the caller already has a channel (or a Path).
  • NetworkSerDe.read(Path, …) and NetworkSerDe.write(Network, ExportOptions, Path) now dispatch on format: for BIN, they open a Files.newByteChannel(path) directly and feed the channel
    constructors — no OutputStream/InputStream adapter.
  • NetworkSerDe.copy() now uses Pipe.SinkChannel/Pipe.SourceChannel. For BIN, the pipe channels are passed directly to BinWriter/BinReader — no Channels.newOutputStream/newInputStream
    adapter.

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
95.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud