[FEATURE] Trigger partition split when the shuffle-server is unhealthy due to the insufficient capacity

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

We found the shuffle-server will slow down the all corresponding spark jobs due the insufficient capacity of localfile store, that also could be caused by the large spark app.

Based on the above oberservation, we should introduce the more aggerative partition split strategy.

### 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 tracing how the shuffle-server detects insufficient localfile-store capacity and how partition splitting is currently handled. The issue does not name files, tests, or a concrete solution; clarify the aggressive split strategy and its expected behavior before implementation. Done should include the new strategy and coverage for the unhealthy-capacity scenario.

Written by the indexing model from the issue text.