Store CBOR serialized transactions in `tx_cbor` table

[sorki]

Description

Optional feature that can be enabled via insert options like so:

 "insert_options": {
    "tx_cbor": "enable",

Testing on preview network, with minimal insert options

  "insert_options": {
    "tx_cbor": "enable",
    "tx_out": { "value": "disable" },
    "ledger": "disable",
    "shelley": { "enable": false },
    "multi_asset": { "enable": false },
    "metadata": { "enable": false },
    "plutus": { "enable": false },
    "governance": "disable",
    "offchain_pool_data": "disable",
    "json_type": "disable"
  }

results in about 6.2GB of data

csyncdb=> SELECT pg_size_pretty(pg_total_relation_size('"public"."tx_cbor"'));
 pg_size_pretty
----------------
 6272 MB
(1 row)

Closes #1701

Checklist

• [x] Commit sequence broadly makes sense
• [x] Commits have useful messages
• [ ] New tests are added if needed and existing tests are updated
• [ ] Any changes are noted in the changelog
• [x] Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
• [x] Self-reviewed the diff

Migrations

• [ ] The pr causes a breaking change of type a,b or c
• [ ] If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
• [ ] Resyncing and running the migrations provided will result in the same database semantically

[sorki]

Added a rollback deletion, schema documentation, changelog entry and hopefully resolved review issues / tests.

[kderme]

Merged at https://github.com/IntersectMBO/cardano-db-sync/pull/1749. Thank you