[FEATURE] Put partition's blockIds info into Spark driver or MR appMaster

### 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

Currently, the partition data's blocks will be stored in the shuffle server, which will cost too much memory. And the less state will benefit maintenance

In #777, a new connection of driver and executor has been created, how about putting the blocks' info into Spark driver or MR appMaster?

### 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!

Start by reviewing the new driver–executor connection referenced in #777 and how partition block information is currently retained in the shuffle server. Compare the Spark driver and MapReduce appMaster entry points, then determine how blockIds could be owned there and how completion would verify that the shuffle server no longer retains this state.

Written by the indexing model from the issue text.