Refactor: reference ports by name instead of repeating the number

[consideRatio]

• Port definitions protocol: TCP is no longer explicitly set
• Ports are now referenced by name from services and network policy ingress
• The deploy/hub and deploy/proxy pods got some ports renamed:
  • hub -> http
  • proxy-public -> http
  • proxy-https -> https
• I removed legacy ports allowed by the deploy/proxy pod's network policy for kube-lego and nginx /health. They could not be accessed anyhow as they were not exposed by the pod.

This should not influence anything.

[consideRatio]

This is to allow ingress to the deploy/proxy's pod, but that pod doesn't expose these ports anyhow. This is not relevant any more.

[consideRatio]

No matter if this goes to the deploy/autohttps or deploy/proxy, both have a port named http even if it is exposed on different port numbers.

[consideRatio]

No matter if this goes to the deploy/autohttps or deploy/proxy, it should always go to the https port unless the https type is "offload", then apparently it should still go through the 443 entrypoint of this service but end up at the http port as it actually is http traffic.

I think the main reason for this, has been to trick anyone using the variables PROXY_PUBLIC_SERVICE_PORT to go to the right location or similar, because that port is the first port exposed by the service. But, anyhow, this is an offtopic discussion with regards to this PR.