Previously we assumed the internal (on the istio gateway) and external (on the user-facing service/ingress) ports were always the same.

This PR introduces deploykf_core.deploykf_istio_gateway.gatewayService.ports.http and deploykf_core.deploykf_istio_gateway.gatewayService.ports.https which can be used to either:

1. Change the ports which the service for the embedded istio gateway listens on:
   • (to potentially make them different from the internal gateway ports, which might help users who want to use the same istio gateway deployment for more than just deployKF)
2. Inform deployKF about which ports are actually seen by end-users:
   • (for users who are bringing their own gateway service, so that deployKF will correctly generate user-facing links with the correct port)

By default, both new deploykf_core.deploykf_istio_gateway.gatewayService.ports values are ~ (null), and the correspondingdeploykf_core.deploykf_istio_gateway.gateway.ports value is used (which is backward-compatible with the current behavior).