fix(expand): use re-exports for non-visibile items

[asterite]

Description

Problem

Part of #8281

Summary

Though it didn't fix any existing test, nargo expand did produce invalid code by using private items. These just produce a warning now but eventually they'll be an error.

You can see what changed in this PR by looking at how the snapshots changed.

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.

[TomAFrench]

Not sure if there's an issue for this but I noticed in the snapshots a few imports like use std::prelude::Vec;. We should be able to just omit any imports from the prelude directory.

[asterite]

Good point.

There are programs in "test_programs" that have imports like this:

use std::collections::vec::Vec;

nargo expand tries to preserve those use to show the expanded program as close to the original program. In this case that import is preserved, except that it's not directly visible so the visible re-export is used. But it's true that nargo expand could check that this use item refers to an item that exists in the prelude, and directly omit it.

In real programs I guess nobody would import these types... but I'll capture an issue anyway.

[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: d395b0c	Previous: b2bfdb7	Ratio
test_report_AztecProtocol_aztec-packages_noir-projects_aztec-nr	4 s	3 s	1.33

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

CC: @TomAFrench