[Feature][Zeta] Support slf4j mdc tracing job id output into logs

[hailin0]

Purpose of this pull request

[Feature][Zeta] Support slf4j mdc tracing job id output into logs

reference
https://www.slf4j.org/manual.html#mdc
https://logging.apache.org/log4j/2.x/manual/thread-context.html#configuration
https://logging.apache.org/log4j/2.x/manual/layouts.html#PatternLayout

subtask of #2725

Does this PR introduce any user-facing change?

No

How was this patch tested?

Added

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config
• Update the release-note.

[hailin0]

[hailin0]

[hailin0]

[hailin0]

https://logging.apache.org/log4j/2.x/manual/thread-context.html#configuration

[Carl-Zhou-CN]

+1

[arshadmohammad]

Good feature, Thanks @hailin0 for working on this.
related to this feature, is there anyway to get all the logs corresponding to job id, using API or command ?

[hailin0]

Good feature, Thanks @hailin0 for working on this. related to this feature, is there anyway to get all the logs corresponding to job id, using API or command ?

@arshadmohammad
The logs of distributed programs(job) are scattered on different machines. What are your thoughts?

[arshadmohammad]

I was looking for functionality similar to mapreduce and yarn, all mapreduce jobs have separate logs.

[hailin0]

I will do some verification later