[HUDI-7626] propagate UserGroupInformation from the main thread to the new thread of timeline service threadpool

[beyond1920]

Change Logs

The UserGroupInformation lost in the new thread of timeline service threadpool. If it does not match the UserGroupInformation from the main thread, the spark writers might failed. See more information in issues#11030.
The pr aims to fix the problem.

Impact

None

Risk level (write none, low medium or high below)

None

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
  ticket number here and follow the instruction to make
  changes to the website.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[hudi-bot]

CI report:

• 2a43774 Azure: PENDING

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[xiarixiaoyao]

we also encounter similar problems in presto. Child threads are unable to correctly inherit UGI information from parent threads. We have made similar modifications in the concurrency methods of HoodieLocalEngine Context and HoodieJavaEngine Context.