Purpose of this pull request

Some config loading log don't take effect about log4j2
When we startup a command like seatunnel.sh -l, the log as follows.

Generally, if you execute commands through some programs, such non-standard logs will be captured in the error log stream, which is very bad

Does this PR introduce any user-facing

How was this patch tested?

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 change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.