[FEATURE] Implement reportShuffleResult with netty proto

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [x] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.

### Describe the feature

I observe the reportShuffleResult decoding in grpc will cost too much cpu time.

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Locate reportShuffleResult and compare its gRPC decoding path with the proposed Netty proto path. Read the surrounding shuffle-result RPC definitions and run relevant decoding or benchmark tests, if present. Done means the Netty proto path is implemented and report results remain correct while decoding CPU cost is reduced.

Written by the indexing model from the issue text.