[BugFix] Ensure query port can be configured in init-password job

[yandongxiao]

Description

A scenario that requires modifying the container listening query port:

1. The source cluster is deployed on virtual machines, while the target cluster is deployed on k8s. External access to the internal IP of k8s is not possible, but pods within k8s can access external IPs.
2. The migration tool is deployed outside of k8s. The StarRocks cluster on k8s is exposed through /etc/host (frontend domain name, node IP of k8s) + NodePort.
3. In the cross-cluster migration tool, use the port obtained from Show Frontend for recording in Frontend. At the same time, use this port to access the target cluster (instead of configuring target_fe_query_port).
4. The target cluster pulls data from the source cluster.

Checklist

For helm chart, please complete the following checklist:

• make sure you have updated the values.yaml
  file of starrocks chart.
• In scripts directory, run bash create-parent-chart-values.sh to update the values.yaml file of the parent
  chart( kube-starrocks chart).

[yandongxiao]

Tested three scenarios:

1. Configuration does not include the query port setting.
2. 2. Configuration includes the query port setting.
3. The query port setting in the configuration is commented out.
   All three scenarios meet expectations.