feat(kuma-cp) new multicluster flow

[jakubdyszkiewicz]

Summary

This PR introduces a new multicluster flow.

Before

When user want to connect Global with Remote they had to

• Deploy Global
• Extract public IP of global and use it in Deploy Remote command
• Wait for Remote to be deployed
• Extract Remote Ingress address
• Apply zone with Ingress address
• 🎉

After

When user want to connect Global with Remote they have to

• Deploy Global
• Extract public IP of global and use it in Deploy Remote command
• 🎉

Full changelog

• Introduced publicAddress and publicPort to Ingress data plane that indicates the address and port that is accessible to other clusters
• Removed flattening of Ingresses, therefore you don't have to have LB for them. Every ingress can have separate public IP
• On Kubernetes, automatically resolve publicAddress and publicPort. It works with both LoadBalancer services and NodePort.
  When LoadBalancer Service waits for its address, we still have an Ingress synced but without public coordinates, which means it won't be used.
  When LoadBalancer Service receives IP, it's automatically updated by Kubernetes controlled, synced to Global, and synced to other Remotes.
  You can override the address and port with annotations if you wish.
• Zone is now automatically created when Remote initiate a stream to Global (which is symmetric with DP that connects to CP creating Dataplane definition)
• Remove Ingress from zones tab in the GUI chore(zones) remove url column kuma-gui#81

Documentation

• In progress