[Bug] multicluster.clusterGateway.port is not propagated to the controller direct URL

Describe the bug

The Helm chart exposes multicluster.clusterGateway.port as a configurable MultiCluster parameter, but the controller's direct ClusterGateway URL is hard-coded to port 9443.

Affected area

Multi-cluster.

For example, rendering the chart with:

helm template demo charts/vela-core \
  --set multicluster.clusterGateway.port=10443 \
  --set multicluster.clusterGateway.secureTLS.enabled=false

produces all of the following:

• ClusterGateway --secure-port=10443;
• ClusterGateway container port 10443;
• Service port/targetPort 10443;
• APIService backend port 10443;
• controller --cluster-gateway-url=demo-cluster-gateway-service:9443.

The default 9443 value does not expose the mismatch.

Expected behavior

When direct ClusterGateway mode is enabled, the controller URL should use the same configured multicluster.clusterGateway.port as the ClusterGateway Service.

Impact

Users who choose a non-default ClusterGateway port can install a manifest whose server and Service use one port while the controller connects to another. Direct multi-cluster operations may then fail to reach ClusterGateway.

KubeVela Version

master at commit 5cf3e3a80ade9d156b60e0691f2c198c3de004ee.

Kubernetes information

Not applicable. The reproduction uses offline Helm rendering with helm template; no live Kubernetes cluster or outage is being claimed.

Duplicate search

I searched open Issues and PRs for multicluster.clusterGateway.port, clusterGateway.port, cluster-gateway-url, and 9443; I did not find a matching Issue or fixing PR.