Enhancements and fixes related to logging, metrics, and testing

[jutaro]

Summary

This pull request addresses multiple enhancements and fixes related to logging, metrics, and testing in the project.

---

Changes

1. Let the Forging Mode metrics respect the command line config

   • Resolves Missing metric for current forging mode on a blockproducer node #5751
   • Fixes a metric to track the current forging mode on a block producer node.
   • Ensures visibility into the forging mode to improve monitoring and debugging.

2. Enhanced Logging for Chain Events

   • Added the following fields to log messages for better traceability:
     • tipBlockHash: Hash of the current tip block.
     • tipBlockParentHash: Hash of the parent block of the tip.
     • tipBlockIssuerVerificationKeyHash: Hash of the verification key of the tip block issuer.
   • Affected log messages:
     • SwitchedToAFork
     • AddedToCurrentChain

3. Consistency Testing for Mainnet Configuration

   • Added a test case to ensure mainnet configuration consistency.
   • Validates the correctness of the mainnet configuration to prevent misconfigurations.

Testing

• Verified the new metric appears correctly in monitoring systems during runtime.
• Confirmed the additional fields are included in the logs for the relevant events (SwitchedToAFork, AddedToCurrentChain).
• Successfully ran the new mainnet configuration test case.

---

Checklist

• Corrected metric for current forging mode.
• Updated log messages with additional fields.
• Implemented and verified the mainnet configuration consistency test.
• Updated relevant documentation if necessary.

---

Linked Issue

Closes #5751

[TerminadaDrep]

Would it be difficult to also enable logging of the reason for "SwitchedToAFork"? IE: Longer chain vs Equal length but terminal block had lower VRF?
That would close feature request 6014

[mgmeier]

@TerminadaDrep I've looked at the issue, and the data traced by SwitchedToAFork would be sufficient to give an underlying cause as to why a certain chain candidate won the Praos ordering over the previous one.
However, determining that cause given the old and new chain selection data needs to be implemented, and is outside the scope of this PR. We'll address it in a future one.

[mgmeier]

LGTM, thank you @jutaro