Switch to babbage era

[ch1bo]

Why

The vasil hard fork is around the corner and it will enable the Babbage era. The hydra-node is targeting only a single era at a time and currently expects Alonzo blocks and transactions. This means, that the hydra-node will likely not work on the testnet/mainnet once they forked to Babbage anymore.

What

We want to support the Babbage era. Prior work has been performed in spike #280. This branch needs to be rebased on top of our latest additions to the Hydra protocol on master. Then, we need to figure out at least two annoyances:

• Babbage does not run on TPraos consensus anymore and hence we don't have BFT-like nodes anymore -> we need to set up proper stake pools for our hydra-cluster tests
• The transaction sequence generators have a new interface / got moved in the cardano-ledger

How

• Rebase babbage-preview and make everything compile (mark failing tests as pending) #406
• Change hydra-cluster tests and benchmarks to stake pool nodes #421
• Use new/updated transaction sequence generators from the cardano-ledger #420
• (optional) Create/revisit test suite running against a testnet #387 and run a manual smoke test against the latest testnet

TBD

• What would happen if we run a pre-babbage, e.g. 0.6.0 version of the hydra-node against a cardano-node on a babbage network?
• Shall we document the hydra-node behavior in regards to hard forks? Related to Hydra node software,scripts & protocol updates #191