chore(cli): Use noir_artifact_cli::fs to read artifacts

[aakoshh]

Description

Problem*

Resolves #7381
Builds on #7384

Summary*

Changes other CLI tools to use the noir_artifact_cli::fs functions to read artifacts.

• inspector (now handles contracts as well)
• profiler (still only expects programs)
• nargo (only executes/infos programs)
• criterion benches

Additional Context

The PR contains some fixes that came out trying to get a more uniform handling of programs vs contracts:

• The ContractFunctionArtifact had brillig_names, but not names; that seems to be the only missing piece to be able to show inspector info about contract functions, so I added it.
• Adds hash to ContractFunctionArtifact so that we can map it back into a CompiledProgram without the loss of information
• Changes the serialisation of hash: u64 to be as String, so that the last digits don't get truncated in the TypeScript types
• Changes the TypeScript representation of hash to number | string for backwards compatibility (although old TS would not read new format)
• I got a test failure due to a mismatch between the hash calculated by nargo and noir-wasm for the contract functions. Unfortunately I didn't notice that for programs they are explicitly deleted by the test until after I debugged the issue to find out that it is down to the FileIds being different, which I was able to fix by changing HashMap to BTreeMap in the wasm compile module. This worked for the test contract, but not the test programs, those still needed the field deleted. Later I understood that nargo adds sources to the FileManager as it visits dependencies, whereas in TypeScript we resolve all dependencies, then add them to the source, and then feed them to the FileManager, so the order is going to be different. Nevertheless I think BTreeMap should at least ensure that TypeScript should agree between different browsers for example, or anything else that could affect the hashes in a HashMap.

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]

Some nits, generally looks good.