fix: top-level item in dependency isn't always visible

[asterite]

Description

Problem

Resolves #9277

Summary

When there's a path foo::bar::baz, it's guaranteed that foo is always visible from where we are at. That's what the code did. However, that logic of "is this is first segment?" was also triggered when dependencies were solved. For example if we have some_dependency::foo::bar::baz, the code would first solve some_dependency, then solve foo::bar::baz starting from that dependency. In that case it's no longer true that the first segment is always visible.

Additional Context

Documentation

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 60a300b	Previous: 6abff2f	Ratio
test_report_AztecProtocol_aztec-packages_noir-projects_noir-protocol-circuits_crates_blob	4 s	2 s	2
test_report_zkpassport_noir_rsa_	1 s	0 s	+∞

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[asterite]

It seems we'd need to change the bignum library so that mod bignum is actually pub mod bignum...

@TomAFrench Do you think we need to wait for that to happen or should we merge this now and eventually fix that?

[TomAFrench]

Looks like there's issues with the semaphore circuit as well. I think it'ld be quicker to just push out some fixes in the libraries rather than going through the effort of disabling these and re-enabling them again.