[FEATURE] Post failure reason when initializing shuffle writer + reader

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

I found many tasks failed on the shuffle writer or reader initialization due to network hang or other problems, but now these errors haven't exposed to the uniffle event logs.

Based on above, we should involve these initialization failures exposed into the event logs.

### 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 shuffle writer and reader initialization and the existing Uniffle event-log path, then identify where network hangs and other initialization failures are currently lost. Done means those initialization failure reasons are exposed in the event logs for both components, with behavior verified using the project's relevant tests.

Written by the indexing model from the issue text.