netConn and msgReader should return io.EOF identically instead of wrapped

[*bufio.Scanner](https://pkg.go.dev/bufio#Scanner) and other consumers of `io.Reader` interface expect to receive `io.EOF` identically when reading to the end of a file/stream.

From the io package:

> // EOF is the error returned by Read when no more input is available.
> // (Read must return EOF itself, not an error wrapping EOF,
> // because callers will test for EOF using ==.)
> // Functions should return EOF only to signal a graceful end of input.
> // If the EOF occurs unexpectedly in a structured data stream,
> // the appropriate error is either [ErrUnexpectedEOF] or some other error
> // giving more detail.
> var EOF = errors.New("EOF")

We currently wrap `EOF` along with any other error when reading from `netConn` or `msgReader`. Instead, we should return `io.EOF` identically to conform with the `io.Reader` spec.

定位 netConn 和 msgReader 的实现，并检查它们如何在输入结束时报告错误。将它们的行为与 io.Reader 要求 EOF 必须以相同方式返回进行比较，然后确认两个 reader 都直接返回 io.EOF，而不是包装后的错误。

由索引模型根据 Issue 内容生成。