[Improvement] Mark app data lost when encountering events dropped

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

When shuffle-server encounters disk problems and triggers the mechanism of dropping events, we should mark the app data lost.

After then, we could reject the write/read requests by these apps to make job fast fail.

### How should we improve?

_No response_

### Are you willing to submit PR?

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

Start by tracing the shuffle-server path that handles disk problems and drops events, then identify where application data-loss state and write/read request handling are defined. Determine how dropped events should mark an application and how subsequent requests should be rejected; the work is done when affected applications fail fast while unaffected applications retain current behavior.

Written by the indexing model from the issue text.