fix(doc): analyze sub-modules imports before self

[asterite]

Description

Problem

nargo doc on noir_base64 would crash

Summary

When a module has pub use foo::bar, the way nargo doc works (and this is how rustdoc works too) is:

• If the publicly exported item can only be accessed via this export, then it's included right under the module that exports it. You can see this in action in the std::ops module where all the traits are actually exposed via a re-export
• Otherwise, the item is shown as a re-export, like here

At one point we also keep track of a module's imports. We process these at the end, so we remove from the HashMap that associates modules with imports, because we'll traverse modules exactly once.

The problem was that because a re-exported module could be added to the module we were processing, it would be re-analyzed, and remove would panic. The solution is to process sub-modules before processing the current module.

This PR also includes an optimization to avoid creating Modules for a dependency multiple times: it was taking a long time to run nargo doc on noir-contracts, but now it works (it takes some times, but at least it ends).

And a couple more things:

• modules and contracts are now distinguished, so a module Foo will show up as "Module Foo" while a contract will show up as "Contract Foo".
• lists (ul) were styled across the entire docs to remove their bullets, but bullets still need to show up in user comments. There's a small CSS fix here to only style the docs layout lists, not user comments lists.

Additional Context

I then ran nargo doc on a few more projects, it works fine an all of them. I'm thinking that it would be nice to eventually run nargo doc on CI on some of the external projects to make sure it works on all of them, but for now maybe not because it could cause slowdowns (to us).

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 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: a5a341f	Previous: 1739efd	Ratio
rollup-checkpoint-merge	0.004 s	0.003 s	1.33
sha512-100-bytes	0.062 s	0.051 s	1.22

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

CC: @TomAFrench

[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: a5a341f	Previous: 1739efd	Ratio
test_report_zkpassport_noir-ecdsa_	3 s	1 s	3

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

CC: @TomAFrench