Raw CBOR datum in transaction outputs

[ch1bo]

Why

When building applications that need to spend from a script UTxO in a Hydra head, which has a datum attached, that off-chain code needs access to the raw Datum for evaluating the transaction and calculate fees.

The schema used by the hydra-node right now matches whatever cardano-api provides, while other applications follow other schemas. For example: kupo, ogmios (also see cardanonical) or blockfrost

This item is a backward-compatible change and in further steps we might want to move to one of those.

What

• Add a inlineDatumRaw to any TxOut sent out by the API, that contains the raw CBOR for any inline datums

How

• Update the API specification and implementation

[ch1bo]

We encountered this when building https://github.com/cardano-scaling/hydra-doom with @Quantumplation and @yHSJ where we use https://github.com/spacebudz/lucid

[ch1bo]

Related to #1509

[ffakenz]

PR upstream: IntersectMBO/cardano-api#632