"feat(#428): enrich /txs response with resolved addresses

[HarunJr]

Summary

Closes #428

The /txs endpoint previously returned raw CBORs as a flat string array. Wallet SDKs like Lace's MidgardChainHistoryProvider require input addresses (HydratedTxIn.address) to classify transactions as Sent or Received — without them, all transactions appear as Received regardless of direction.

Breaking Change

Response shape updated from:

{ "txs": ["<cbor_hex>"] }

to:

{
  "txs": [
    {
      "cbor": "<cbor_hex>",
      "resolvedInputs": [{ "txHash": "...", "index": 0, "address": "addr_test1..." }]
    }
  ]
}

Changes

• address_history gains direction and outref columns to distinguish senders (input) from receivers (output) per UTxO
• Input addresses are resolved at insert time by looking up spent outrefs in mempool_ledger before they are cleared no extra lookups needed at query time
• ProcessedMempoolDB included in retrieve() so in-flight transactions remain visible during the block confirmation window
• CML WASM objects explicitly freed after use to prevent heap leaks under sustained load
• Effect.all concurrency capped at 20 to prevent DB connection pile-ups on large tx histories
• Existing DBs handled via migrate() called in InitDB on startup no manual intervention needed
• CORS middleware added to the HTTP server so browser-based wallet clients (e.g. Lace) can call the node endpoints cross-origin

Test plan

• All 18 database tests pass (docker compose --profile test run --rm midgard-node-tests)
• /txs?address=... returns resolvedInputs with sender address populated for L2 transfers
• Self-transfers correctly show the wallet's own address in resolvedInputs
• Deposits return resolvedInputs: [] (no L2 inputs)

---