feat(nargo): Version info in nargo and wasm

[kobyhallx]

Related issue(s)

#720 Version Hash in Nargo and wasm

Resolves #720

Description

Both Nargo and Wasm binary of noir compiler should allow to identify them based on compile time information.

Summary of changes

Adds compilation time git version hash, indication if it was build from dirty git tree.
Same applies to changes in WASM which exposes function to get this information.

Dependency additions / changes

N/A

Test additions / changes

N/A

Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt with default settings.
• I have linked this PR to the issue(s) that it resolves.
• I have reviewed the changes on GitHub, line by line.
• I have ensured all changes are covered in the description.
• This PR requires documentation updates when merged.

Additional context

N/A

[TomAFrench]

@kobyhallx When building fdfb71f locally I get many changes appearing in Cargo.lock compared to what's committed. Do you get this as well? We should ensure that CI fails appropriately in this case.

[TomAFrench]

Looks good, my main issue is with the lockfile atm.

[phated]

Have we looked at https://crates.io/crates/build-info ? It says it separates the git deps out so they aren't being pulled in by build. It also has WAY more downloads than the build-data crate

[kobyhallx]

Have we looked at https://crates.io/crates/build-info ? It says it separates the git deps out so they aren't being pulled in by build. It also has WAY more downloads than the build-data crate

build-info seems to bring runtime dependency though. Also build-data makes it more transparent how to escape in alternative build scenarios like with no git available in pure nix builds.

[TomAFrench]

LGTM