Fix global_slot_since_genesis query

[martyall]

what it does

• closes #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

[martyall]

!ci-build-me

[svv232]

!ci-build-me