fix: GoTLS destination port hardcoded in eBPF probe

[mayankpande88]

Problem

ebpftracer/ebpf/l7/gotls.c:222 has a TODO:

// TODO: Extract actual destination port from socket instead of hardcoding

Go TLS connections don't have accurate destination port attribution. This affects connection tracking for Go-to-Go TLS traffic.

Fix

Extract the destination port from the socket's inet_sock struct in the eBPF probe, similar to how socket_info.c does it for TCP connections.

Impact

Medium — incorrect destination attribution for Go TLS traffic.