Support tracing Istio managed services

[yzhao1012]

Is your feature request related to a problem? Please describe. Today, Pixie’s service map uses remote IP address to derive the Pod name for RPC messages between micro-services. In the case of Istio managed cluster, envoy proxy terminates TCP connections, and RPC messages would use envoy’s address as remote IP. That breaks the logical connection between the client & server, which are mediated by service message proxy.

Describe the solution you'd like Update relevant PXL scripts to replace local IP address 127.0.0.* with the source pod or service name.

Also support tracing Envoy TLS traffic, by implementing tracing envoy (with boringssl).

Describe alternatives you've considered There is no obvious alternative.

Additional context N/A