[Improvement] Optimize local disk selection strategy

### 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 want to raise this issue to improve stability when using MEMORY_LOCALFILE storage type. Maybe some issues will be as sub-tasks in this improvement.

The first improvement is to avoid all apps fail when single disk capacity reaches high-watermark. We could do below optimizations.

1. Introduce the metrics of TOP10 apps which use the number of written bytes #333 .
2. Introduce the free space & total space metrics of every local disk
3. Introduce the pluggable disk selection strategy. Currently the disk will be selected based on the hash. Free-capacity based strategy should be supported.
4. Allow app write data to another disk when encountering the corresponding disk reaching high-watermark #306

### How should we improve?

_No response_

### Are you willing to submit PR?

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

No files, tests, or entry points are named. Start by locating the MEMORY_LOCALFILE storage implementation and its current hash-based disk selection, then review issues #333 and #306. Done would require an agreed scope and design for disk metrics, pluggable or free-capacity-based selection, and fallback when a disk reaches its high-watermark.

Written by the indexing model from the issue text.