Update to vergen 5, add branch, commit time, and build target to the panic metadata, automatically update app version from crate version

[fanatid]

Motivation

Add more metadata with vergen crate.

Solution

Update vergen to version 5.

Review

I wanted add rustc metadata but this requires sentry update for the new version of rustc_version.

Related Issues

• Require Update dependencies to support Apple M1, fix Windows CI LLVM paths #2026
• Closes Upgrade to vergen 5 #1741
• Implements some of Use git metadata and platform info in Zebra #692

Follow Up Work

Update sentry crate (require tokio 1 😢 + sentry-tracing update: kellpossible/sentry-tracing#1) and add rustc metadata.

[teor2345]

Thanks I've been waiting for these for a while.

[teor2345]

• Implements some of Use git metadata and platform info in Zebra #692

I edited this line, because GitHub reads "partially resolve #ticket" as "resolve #ticket", and auto-closes the ticket.

[teor2345]

• Require Update dependencies to support Apple M1, fix Windows CI LLVM paths #2026

Yeah we really do need to move to the latest cc crate version, it's blocking a bunch of changes.

[teor2345]

Looks good, let's merge if CI passes.

[teor2345]

Looks like we might need a metrics-exporter-prometheus update before we can merge this change:

error: failed to select a version for `cc`.
    ... required by package `libgit2-sys v0.12.18+1.1.0`
    ... which is depended on by `git2 v0.13.17`
    ... which is depended on by `vergen v5.1.1`
    ... which is depended on by `zebrad v1.0.0-alpha.6 (/zebra/zebrad)`
versions that meet the requirements `^1.0.43` are: 1.0.67, 1.0.66, 1.0.65, 1.0.64, 1.0.63, 1.0.62, 1.0.61, 1.0.60, 1.0.59, 1.0.58, 1.0.57, 1.0.56, 1.0.55, 1.0.54, 1.0.53, 1.0.52, 1.0.51, 1.0.50, 1.0.49, 1.0.48, 1.0.47, 1.0.46, 1.0.45, 1.0.44, 1.0.43

all possible versions conflict with previously selected packages.

  previously selected package `cc v1.0.41`
    ... which is depended on by `generator v0.6.23`
    ... which is depended on by `loom v0.3.6`
    ... which is depended on by `sharded-slab v0.1.0`
    ... which is depended on by `metrics v0.13.0-alpha.8 (https://github.com/ZcashFoundation/metrics?rev=971133128e5aebe3ad177acffc6154449736cfa2#97113312)`
    ... which is depended on by `metrics-exporter-prometheus v0.1.0-alpha.7 (https://github.com/ZcashFoundation/metrics?rev=971133128e5aebe3ad177acffc6154449736cfa2#97113312)`
    ... which is depended on by `zebrad v1.0.0-alpha.6 (/zebra/zebrad)`

[teor2345]

Looks like we might need a metrics-exporter-prometheus update before we can merge this change:

Here's what I tried:

Merge the most recent version of metrics-exporter-prometheus that doesn't use tokio-1.0 with the tokio-0.3 changes in the Foundation's metrics fork:
https://github.com/teor2345/metrics/tree/tokio-0.3%2Bmetrics-exporter-prometheus-v0.1.0-alpha.12

Update Zebra to use that branch:
https://github.com/teor2345/zebra/tree/vergen

But I get a metrics exporter acceptance test failure - it doesn't provide any output.

We had this issue once before when there was a version mismatch in some dependencies, so it should be fixable. But I might not have time to look at it for a few days.

[teor2345]

We had this issue once before when there was a version mismatch in some dependencies, so it should be fixable. But I might not have time to look at it for a few days.

It was #1349, duplicate metrics dependencies. Seems like my attempt had similar issues.

[fanatid]

We do not need to update metrics-exporter-prometheus for the new vergen.

[teor2345]

Looks like merging the latest main branch fixed it all up.

[dconnolly]

Looks like this is broken inside a gcloud build because the source is copied into a container image build and the git info injected as env vars, with no .git or associated env data present: #2037