Fix Go workspace member loading from cache

When a workspace member requires another workspace member, the code
should not try to load it from the module cache. Go builds workspace
members (main modules) from their local directories and ignores version
requirements for them.

The fix filters out requirements that point to workspace members when
building the module graph, both in the initial queue and when adding
transitive dependencies.

Author: cursoragent

crates/socket-patch-core/src/vendor/go_workspace.rs

@@ -395,6 +395,7 @@ impl GoWorkspace {
             .iter()
             .filter_map(|m| m.go_mod.as_deref())
             .flat_map(go_mod_edit::parse_required_versions)
+            .filter(|(path, _)| self.main_module(path).is_none())
             .map(|(path, v)| (path, v, false))
             .collect();
         while let Some((path, version, unpruned)) = queue.pop_front() {
@@ -411,7 +412,9 @@ impl GoWorkspace {
             };
             if unpruned || !dep.pruned {
                 for (p, v) in &dep.requires {
-                    queue.push_back((p.clone(), v.clone(), true));
+                    if self.main_module(p).is_none() {
+                        queue.push_back((p.clone(), v.clone(), true));
+                    }
                 }
             }
         }