Fix global_slot_since_genesis query

[martyall]

what it does

• closes Graphql command fork_config returning global slot since hf instead of global slot since genesis #15614
• fixes logger bug that prevented showing the s3 ledger tar hash in an error message

how I tested

I synced to mainnet and ran the query there:

> curl -g -X POST -H "Content-Type: application/json" -d '{"query":"query { fork_config }"}' http://127.0.0.1:3085/graphql

{"data":{"fork_config":{"proof":{"fork":{"state_hash":"3NK4BpDSekaqsG6tx8Nse2zJchRft2JpnbvMiog55WCr5xJZaKeP","blockchain_length":359605,"global_slot_since_genesis":564480}}

So the global_slot_since_genesis came back as 564480 at block height 359605, which seems right.

Checklist:

• Dependency versions are unchanged
  • Notify Velocity team if dependencies must change in CI
• Modified the current draft of release notes with details on what is completed or incomplete within this project
• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? List them

[svv232]

good stuff! I have also verified the test output for this graphql call on a mina daemon connected to devnet.

[mrmr1993]

Could you redirect this towards the compatible branch? The master branch is generally for changes that we've already released (although can include infra changes as needed), whereas compatible are those soft-forkable changes that we're staging for release.

[martyall]

!ci-build-me

[svv232]

!ci-build-me

[martyall]

!ci-build-me

[svv232]

!ci-build-me

[martyall]

!ci-build-me

[martyall]

@mrmr1993 @MinaProtocol/infra-eng-reviewers Can someone with authority please review this change?

[mrmr1993]

!ci-build-me

[mrmr1993]

!ci-build-me