feat(nargo): include short git commit in cli version output

[TomAFrench]

Related issue(s)

Resolves #720

Description

Summary of changes

I've added some macros which append the current git hash onto the version returned by clap so we now get the output:

$ nargo --version
nargo 0.1.0 (git:d4154364)

If there are uncommitted changes to the repo then the git hash is suffixed with -dirty to alert us that it's not running the exact code from that commit.

At the same time, I've made clap always pull the version from cargo.toml so we don't need to manually keep this in sync.

Dependency additions / changes

The following dependencies are added to nargo:

• git_version as this allows us to get the git hash in a non-hacky way which handles incremental compilation correctly.
• const_format in order to format the cargo version and git hash together.

Test additions / changes

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.

Additional context

[guipublic]

If there are uncommitted changes to the repo then the git hash is suffixed with -dirty to alert us that it's not running the exact code from that commit.

Can you explain this? If changes are not committed, then obviously it is not part of the commit, so I don't understand.

[TomAFrench]

Yes but if I check out a particular commit, make a bunch of changes to the code, and then build nargo without committing those changes then nargo would still report that same commit hash despite it no longer corresponding to the code being run. This is potentially misleading so adding a suffix seems sensible.