POC feat(symbolization): Add DWARF symbolization with debuginfod support

[marcsanmi]

Context

This PR introduces a POC implementation for DWARF debug information symbolization. The implementation can fetch debug info from debuginfod servers or local files and resolve memory addresses to source code locations.

Key features

• Remote debug info fetching via debuginfod
• Local debug info file support
• DWARF debug info parsing and address resolution
• Support for inline function resolution
• Memory address normalization for different ELF types

Note: While this POC demonstrates the core symbolization functionality, a production-ready implementation would require several additional components: a robust debuginfod client with retries and rate limiting, proper caching mechanisms, fallback symbolization methods (e.g., symtab) when DWARF isn't available, better error handling, and security considerations around file handling and network requests.

To run it:

1. Run the main program with default debuginfod server and buildID
2. Optionally modify the client to use a local debug info file
3. Optionally enable SymbolizeAll to explore all available symbols

Example usage in main.go shows both specific address symbolization and full binary exploration (commented out by default as they are alternative approaches).

[korniltsev]

would be nice to have some benchmarks of symbolizing different amount of locations and different file sizes, I think it can help us to pick the right place and architecture for using this

[korniltsev]

nit: this may cause a path traversal, allowing somebody to specify buildID as ../../.../ we should sanitize user provided data in buildID