Make metadata pod lookups more resilient to short lived processes

[ddelnano]

Summary: Make metadata pod lookups more resilient to short lived processes

This is a continuation of the work started from #1989. Since the local_addr column is populated for client side traces, it can be used as a fallback lookup for these traces. This doesn't solve all of the permutations of missing short lived processes (#1638), but provides more coverage than before.

Relevant Issues: #1638

Type of change: /kind bugfix

Test Plan: Verified the following

• Compared the performance with and without this change with src/e2e_test/vizier/exectime:exectime. This change has a minor performance impact, but it closes the gap on certain situations that previously caused users to distrust Pixie's instrumentation

# Performance baseline
$ ./exectime benchmark -a testing.getcosmic.ai:443 -c <cluster_id> 2>&1 | tee baseline_for_simple_udf_swap_e20880ffd.txt
# Performance of this change
./exectime benchmark -a testing.getcosmic.ai:443 -c <cluster_id> 2>&1 | tee simple_udf_swap_cd217c05c.txt

simple_udf_swap_cd217c05c.txt
baseline_for_simple_udf_swap_e20880ffd.txt

• Ran for i in $(seq 0 1000); do curl http://google.com/$i; sleep 2; done within a pod and verified that with this change all traces are shown, without this change a significant number of traces are missed. See before and after screenshots below:

Changelog Message: Fix a certain class of cases where Pixie previously missed protocol traces from short lived connections