[system-probe] Add static binary inspection to create lookup tables for crypto/tls.(*Conn).{Read,Write,Close} - copy

[einat-stern]

See this PR for previous discussion

What does this PR do?

This PR builds on the work done in #10039 to add another set of lookup tables that are generated ahead-of-time from a suite of Go versions/architectures-- this time, to contain information about the layout of structs and function arguments/return values that is useful to trace TLS traffic running through the standard library. Doing so requires knowledge about:

• The position of arguments from each of crypto/tls.(*Conn).Read, crypto/tls.(*Conn).Write, andcrypto/tls.(*Conn).Close
• The layout of structs needed to extract the socket file descriptor from a crypto/tls.(*Conn) value (there are a handful of around 5 pointer/struct embeds that each need to have offsets)

The rest of the information needed to attach probes is able to be determined at runtime, even if the debug/ELF symbols have been stripped from a binary (as opposed to the above two sets of data), so some of it was excluded from this PR (namely, static interface-table entries and runtime.g pointer location information), and is instead in #10161.

Motivation

Tracing Go HTTPS traffic using eBPF.

• [system-probe] Add Go HTTPS tracing eBPF probes #10161

Additional Notes

I'm not sure whether the changes I made to generate_tools.go are appropriate.

Possible Drawbacks / Trade-offs

The lookup table generation for the binary-inspected data is only run on minor-version bumps (and the latest beta/RC version), so in the unlikely case that the language introduces changes on a revision-level version bump, those changes won't be detected by this implementation.

Describe how to test/QA your changes

Running inv -e system-probe.generate-lookup-tables should run the loookup table generation logic using go generate .... The output file will be at pkg/network/http/gotls/lookup/luts.go, and should be the same as the one currently in the PR.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• The appropriate team/.. label has been applied, if known.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the config template has been updated.