[Fix][Config] Fix invalid telemetry-log config in seatunnel.yaml

[mrtisttt]

Purpose of this pull request

There is an incorrect configuration in config/seatunnel.yaml, which will cause an error to be reported in the logs when starting the Seatunnel service.

config/seatunnel.yaml:

seatunnel:
  engine:
		……
    telemetry:
      metric:
        enabled: false
      log:
        scheduled-deletion-enable: true

When using this configuration, there will be warnings in the service logs:

[] 2025-04-25 15:06:22,410 WARN  [amlSeaTunnelDomConfigProcessor] [main] - Unrecognized element: log

The correct configuration should be "logs" instead of "log":

seatunnel:
  engine:
		……
    telemetry:
      metric:
        enabled: false
      logs:
        scheduled-deletion-enable: true

Does this PR introduce any user-facing change?

No.

How was this patch tested?

When the service starts, it can correctly parse the corresponding configuration.

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.

[Copilot]

Pull Request Overview

This PR fixes an invalid telemetry configuration in seatunnel.yaml that causes log warnings during service startup.

• Correct the telemetry logging configuration by renaming "log" to "logs".
• Ensures that the Seatunnel service correctly parses the telemetry configuration without generating warnings.

[Copilot]

Renaming 'log' to 'logs' fixes the misconfiguration issue that causes warnings in the service logs.

[Hisoka-X]

Hi @mrtisttt , why closed this?

[mrtisttt]

Hi @mrtisttt , why closed this?

Hi, I'm concerned whether this fix will be too simplistic. Although it does solve the problem. I'll reopen it to check if it needs to be merged. I'm just starting to get involved in this project recently.

[Hisoka-X]

LGTM. Thanks @mrtisttt . cc @corgy-w