Revert event loop related changes

[shangm2]

Description

1. we see some issues at certain clusters where workers are not receiving any splits. Reverting the following two prs back to unblock others so I can take time to root cause it.
   a. Use a wrapper for event loop to handle exceptions gracefully #24412
   b. Assign event loop to tasks and run a task's methods in the same loop #24288

Motivation and Context

1. reverting event loop related changes to unblock others.

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* ... 
* ... 

Hive Connector Changes
* ... 
* ... 

If release note is NOT required, use:

== NO RELEASE NOTE ==

[jainxrohit]

Thank you Shang!

[rschlussel]

thanks @shangm2 can you fix the merge conflict?

FYI @ZacBlanco this change was in the 0.291 release. We're still investigating, but that release may need to be patched.

[arhimondr]

We are still investigating the problem. There is a chance it could be related to differences in configuration on our side. Let's hold on with the revert for now.

[rschlussel]

rebase onto master instead of adding a merge commit

we'll revert this for now while we investigate and figure out how to put these changes behind a config in case of regression.

[shangm2]

rebase onto master instead of adding a merge commit

@rschlussel let me know if I should keep two revert commits so it is easy for eyes or I should squash them together. Thanks!

[rschlussel]

I don't care either way.

[arhimondr]

figure out how to put these changes behind a config in case of regression

We may need to create a copy of the HttpRemoteTask/TaskInfoFetcher/ContinuousTaskStatusFetcher and change the HttpRemoteTaskFactory to create current / old one based on a property.

Is it confirmed that this change is the change causing issues?

[rschlussel]

No it's not confirmed. We still don't know the root cause.

[shangm2]

figure out how to put these changes behind a config in case of regression

We may need to create a copy of the HttpRemoteTask/TaskInfoFetcher/ContinuousTaskStatusFetcher and change the HttpRemoteTaskFactory to create current / old one based on a property.

Is it confirmed that this change is the change causing issues?

Will do.

[jainxrohit]

figure out how to put these changes behind a config in case of regression

We may need to create a copy of the HttpRemoteTask/TaskInfoFetcher/ContinuousTaskStatusFetcher and change the HttpRemoteTaskFactory to create current / old one based on a property.

Is it confirmed that this change is the change causing issues?

This is a good suggestion!