[Improvement] Independent rust based shuffle server project

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

### What would you like to be improved?

I hope the rust based shuffle-server could be as a independent project, like the paimon-rust? I don't hope the rust CI/release blocked the master branch development. BTW, the independent project will speed up the release and development.

BTW, I think I will devote this in the next months. I'm always optimizing this in my forked branch.

### How should we improve?

_No response_

### Are you willing to submit PR?

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

Start by reviewing the existing Rust-based shuffle-server project and the Rust CI and release workflows it currently shares with the master branch. Compare those boundaries with the forked branch mentioned in the issue, then define what an independent project would include and how its development, CI, and releases should be separated.

Written by the indexing model from the issue text.