Spike: Switch to babbage and use serializeBuiltinData

[ch1bo]

What & Why

To help on testing and releasing the Babbage scope, we want to be an "early adopting" DApp prior to the Vasil HF.

In this effort we need to switch to the newly created Babbage era and use it in our Chain access components and connect to a pre-release cardano-node on the corresponding testnet.

Furthermore, this allows us to test drive the requested-by-us (as CIP) serialiseBuiltinData builtin and report on the improvement we get by it.

Scope

• Update cardano-node and cardano-ledger code to some pre-release version
• Switch to using Babbage era in our chain access code
  • Optional: also switch the embedded ledger's era if it makes things easier
• Use serialiseBuiltinData instead of our on-chain-CBOR-encoder
• Report new transaction size and execution costs results
• Report any issues encountered along the way

Tasks

• Update dependencies and create babbage-preview branch #339
• Migrate scripts to PlutusV2 to, use serializeData and benchmark tx-cost #353

[ch1bo]

Labelled 🔴 because this was not discussed yet and I added it to keep track.

[ch1bo]

Discussed this in planning session and with added scope we deem this to be 🟢. Also prioritized this up to provide feedback to plutus early and be in a position to verify this feature for vasil HF.

[ch1bo]

Closed by creating draft PR #355

[ch1bo]

We intend to derive a follow-up feature of actually switching to PlutusV2 and Babbage in our next planning session.