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

[zuston]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues 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!