Improve Go component dependency resolution

[avrabe]

Problem

Go component support has limitations in dependency resolution that affect complex projects:

Issues

1. Go binary not found warnings - Build system cannot locate system Go for dependency resolution
2. Missing go.sum entries - Some components fail due to missing dependency checksums
3. Module resolution failures - Complex Go module dependency graphs not fully resolved
4. TinyGo upstream limitations - Some standard library features not available in TinyGo

Current Workarounds

• Go components with complex dependencies excluded from CI
• Warning messages displayed but builds continue where possible
• Some Go examples marked as manual

Requirements for Resolution

• Improve Go binary detection in Bazel sandbox environment
• Better integration with Go module system for dependency resolution
• Enhanced error handling for missing go.sum entries
• Document TinyGo limitations and workarounds
• Add comprehensive Go component integration tests

Priority

Medium - Basic Go components work, but complex dependencies have issues

Related Files

• //go/*
• //examples/go_component/*
• //toolchains/tinygo/*

Context

This affects the TinyGo toolchain integration and is not a regression from the rules_rust 0.65.0 upgrade.