feat(logs): prints git metadata and platform info when zebrad starts up

[arya2]

Motivation

To make it easier for user to find git metadata and platform info for their bug reports.

Closes #3111

Solution

Logs the panic metadata at info level when starting a zebrad server

Review

Anyone can review this PR

Reviewer Checklist

• Logs git and build metadata when running zebrad start or copy-state commands

[teor2345]

Would you mind showing us what the output looks like in the logs?

[codecov]

Codecov Report

Merging #5200 (eae5002) into main (202dc43) will decrease coverage by 0.05%.
The diff coverage is 75.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5200      +/-   ##
==========================================
- Coverage   79.14%   79.09%   -0.06%     
==========================================
  Files         307      307              
  Lines       39218    39224       +6     
==========================================
- Hits        31040    31023      -17     
- Misses       8178     8201      +23     

[arya2]

Would you mind showing us what the output looks like in the logs?

Looks like

2022-09-20T16:04:29.201116Z  INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::TRACE LOG_STATIC_MAX_LEVEL=Trace
2022-09-20T16:04:29.201524Z  INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0-unofficial-test.4+30.geae5002
Zcash network: Mainnet
state version: 25
branch: log-git-metadata-on-start
git commit: eae5002
commit timestamp: 2022-09-20T15:59:47Z
target triple: x86_64-unknown-linux-gnu
build profile: debug

[teor2345]

Would you mind showing us what the output looks like in the logs?

Looks like

Looks great!

[teor2345]

Would you mind using GitHub keywords to link issues and PRs?
GitHub automatically closes the issue when the PR closes, but ZenHub doesn't.

I usually put:
Closes #3111
in the PR description. (Adding it to comments doesn't work.)

https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

[upbqdn]

LGTM.