[Feature][Connector-V2] Add tunnel_name option to MaxCompute Connector

[xxzuo]

Purpose of this pull request

adds a new configuration option tunnel_name to the MaxCompute connector to support specifying a custom Tunnel Quota (exclusive resource group) for data transfer operations.

Tunnel Quota allows users to use dedicated computing resources for MaxCompute Tunnel data transfer, providing better performance and resource isolation.

close #10684

Does this PR introduce any user-facing change?

This PR adds a new configuration option tunnel_name to the MaxCompute connector.

New option:

Name	Type	Required	Default
tunnel_name	String	No	-

Documentation:

• Added tunnel_name option description in both English and Chinese docs for Source and Sink connectors
• Documented the important limitation: Tunnel Quota only works with VPC (Virtual Private Cloud) endpoints, not supported for public network access

How was this patch tested?

Verified in local development environment.Tunnel Quota feature only takes effect when the user has purchased exclusive data transmission resources and uses VPC endpoints, without these conditions, the configuration has no functional impact on runtime

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 necessary, please update incompatible-changes.md to describe the incompatibility caused by this PR.
• 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

[Copilot]

Pull request overview

Adds support for configuring a MaxCompute Tunnel Quota (exclusive resource group) via a new tunnel_name option in the MaxCompute connector, and documents the option in both English and Chinese connector docs.

Changes:

• Add tunnel_name option to MaxCompute connector configuration options.
• Apply tunnel_name to TableTunnel configuration by setting the Tunnel quota name.
• Document tunnel_name (and list tunnel_endpoint) in source/sink docs (EN/ZH), including the VPC endpoint limitation.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
seatunnel-connectors-v2/connector-maxcompute/src/main/java/org/apache/seatunnel/connectors/seatunnel/maxcompute/util/MaxcomputeUtil.java	Sets Tunnel quota name on TableTunnel when tunnel_name is provided.
seatunnel-connectors-v2/connector-maxcompute/src/main/java/org/apache/seatunnel/connectors/seatunnel/maxcompute/config/MaxcomputeBaseOptions.java	Introduces new config option tunnel_name.
docs/zh/connectors/source/Maxcompute.md	Documents tunnel_endpoint and tunnel_name for the source connector (ZH).
docs/zh/connectors/sink/Maxcompute.md	Documents tunnel_name and lists tunnel options in the sink options table (ZH).
docs/en/connectors/source/Maxcompute.md	Documents tunnel_endpoint and tunnel_name for the source connector (EN).
docs/en/connectors/sink/Maxcompute.md	Documents tunnel_name and lists tunnel options in the sink options table (EN).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[DanielLeens]

I pulled this PR locally and walked the option -> client configuration path. The new tunnel_name option is plumbed from MaxcomputeBaseOptions into MaxcomputeUtil.getTableTunnel(), and it is only applied when configured, so the default behavior stays unchanged. I do not see a blocking issue in the current revision.