fix: some nargo expand fixes

[asterite]

Description

Problem

For AztecProtocol/aztec-packages#15971

Summary

This mainly fixes an issue I knew about, but didn't consider it a priority to fix: calls generated by macros could refer to traits that are not in scope, if they are done using macro calls like get_trait_impl, then methods, etc. nargo expand will now check if the trait related to the call is in scope and, if not, use <Type as Trait>::method to call it.

While doing this I noticed that nargo expand would also not put unquote markers, so I fixed that too.

Additional Context

I think we should put a disclaimer somewhere that nargo expand is mostly a debugging tool and that it will try its best to produce code that compiles, but it won't always be possible (even if we fix all bugs). For example if a macro inserts a struct value, nargo expand will show it as Struct { field1: value1, field2: value2, ... } even though those fields might be private.

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: 7938e46	Previous: d35a767	Ratio
test_report_AztecProtocol_aztec-packages_noir-projects_noir-protocol-circuits_crates_private-kernel-lib	2 s	1 s	2

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

CC: @TomAFrench

[TomAFrench]

Are there any ignored nargo expand tests which need to be removed from the list of tests in the build.rs file?

I think we should put a disclaimer somewhere that nargo expand is mostly a debugging tool and that it will try its best to produce code that compiles, but it won't always be possible (even if we fix all bugs). For example if a macro inserts a struct value, nargo expand will show it as Struct { field1: value1, field2: value2, ... } even though those fields might be private.

Agreed that we should highlight that this is done on a best-efforts basis.

[TomAFrench]

LGTM, only question is whether we can take some more tests off of the ignore list.

[asterite]

@TomAFrench Good point. I changed the tests so we can now when they start passing and, indeed, some more tests passed.

[github-actions]

⚠️ Performance Alert ⚠️

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

Benchmark suite	Current: 3523a83	Previous: 8146755	Ratio
rollup-block-root-single-tx	254 s	196 s	1.30

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

CC: @TomAFrench