Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(scripts,chart): rename OVN_{NB,SB}_PORT to avoid Kubernetes env clash

CI is failing on every job at the kube-ovn-cni daemonset rollout. Root
cause: Kubernetes auto-injects environment variables for in-namespace
Services using the pattern `<SVCNAME>_PORT=tcp://<ClusterIP>:<port>`.
The Service named `ovn-nb` therefore implicitly creates
`OVN_NB_PORT=tcp://10.x.x.x:6641` in every kube-system pod's env, which
collided with the new variable I introduced in this PR for the
external-endpoint port. kube-ovn-controller then built a garbage
connection string like

    --ovn-nb-addr=tcp:[172.18.0.3]:tcp://10.110.227.251:6641

so the OVN agents never came up.

Rename the variable everywhere to `KUBE_OVN_NB_PORT` /
`KUBE_OVN_SB_PORT` — the kube-ovn project prefix is unique and avoids
the kubelet's auto-injected names. Touch points:

- dist/images/start-controller.sh
- dist/images/start-ic-controller.sh
- dist/images/start-ovs.sh
- charts/kube-ovn/templates/controller-deploy.yaml
- charts/kube-ovn/templates/ic-controller-deploy.yaml
- charts/kube-ovn/templates/ovsovn-ds.yaml

The Helm-internal helper names (`kubeovn.ovnNbPort` /
`kubeovn.ovnSbPort`) stay unchanged; only the env vars they generate
into pods got renamed. The defaults (6641/6642) still mean
in-cluster Service mode for non-Kamaji installs.

Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>