[FR] - Update kes-period-info to check counter on Babbage

[CarlosLopezDeLara]

After the hardfork we will only be able to bump the op cert counter by exactly 1. We will need to:

• Update the command to do this check in the Babbage era onwards.
  Perhaps include an --output-counter flag (optional) that gives you counter for the pool at the right value to issue a new opcert.
• Update documentation to reflect this requirement/restriction. https://github.com/input-output-hk/cardano-node/blob/master/doc/stake-pool-operations/KES_period.md --> PR#4116

From #3945

Reference: https://input-output-rnd.slack.com/archives/C02CHLB0BU4/p1654081538236349?thread_ts=1654078816.490359&cid=C02CHLB0BU4

[dcoutts]

I note that this command also appears to need to use the query for the protocol state, which is a somewhat unstable format. It'd be better if "production" commands (as opposed to debug state dump commands) used specific queries rather than poking about in the protocol state or ledger state. That way we can make them backwards compatible more easily.

[CarlosLopezDeLara]

Lowering priority since kes-period-info "as is" already provides the required information. Adding --output-counter would be an enhancement.