[FEATURE] eager shuffle deletion for Spark

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

Eager deletion of Spark shuffle data for completed stages is preferable, because the native Spark cleanup mechanism is too slow to reclaim resources in a timely manner.

celeborn also has similar design. https://github.com/apache/celeborn/pull/3569

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

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

The issue names no repository files, tests, or entry points. Start by tracing how Spark reports completed stages and how Uniffle currently cleans up shuffle data, then compare the referenced Celeborn design. Done requires a defined eager-deletion approach, implementation scope, and validation that completed-stage resources are reclaimed safely.

Written by the indexing model from the issue text.