Applications bound to localhost behind the Service are reachable when Kuma deployed

[lukidzi]

What happened?

When the application running within a Pod is bind to the localhost, has a Service that exposes it and we deploy Kuma, you can reach the application. But the request to the application bind to podIP is failing. We should be more consistent with migration for users and increase security by not exposing localhost bound applications.

Step to reproduce:

1. Deploy Kuma
2. Deploy demo application bound to localhost and expose it by the Service
3. Install another pod with curl/wget
4. Request CLUSTER_IP:PORT from the client pod
5. request will pass

Step to reproduce case with pod IP:

1. Deploy Kuma
2. Deploy demo application bound to podIP and expose it by the Service
3. Install another pod with curl/wget
4. Request CLUSTER_IP:PORT from the client pod
5. Request will fail

Deployment without the mesh has different behavior and request to application bound to localhost fail while to podIP its success.