interop: fromda DB

[protolambda]

Description

Depends on #12427

Simplified from-da DB, that always encodes both the L1 and L2 block as part of the same entry.

For a year of data, at 1 second block time, 100 bytes per entry, that would be 365 * 24 * 60 * 60 * 100 = 3,153,600,000, or about 3 GB. And with the single-type fixed-width append-only entries, it should be robust against corruption on restart, and easily sliced/diced/shared.

This generalized the entry-DB with generics such that we can use a custom entry type, and customize the entry size.

Tests

• Tests that check all the AddDerived error cases
• Tests that cover the empty / single-entry type edge-cases
• Test that queries a randomly generated series of derived/derived-from additions
• Parameterized testing of the above to cover cases where L1 and L2 start from a non-0 block.

Additional context

Supersedes draft 1 from here: #12428
and prior entry-db generalization work.

Metadata

Fix #12076

[semgrep-app]

Semgrep found 3 sol-style-require-reason findings:

• packages/contracts-bedrock/scripts/deploy/Deploy.s.sol
  • L1002 - Triage
  • L1083 - Triage
  • L1090-1093 - Triage

require() must include a reason string

_{Ignore this finding from sol-style-require-reason.}

Semgrep found 2 golang_fmt_errorf_no_params findings:

• op-supervisor/supervisor/backend/db/query.go
  • L93 - Triage
  • L97 - Triage

No fmt.Errorf invocations without fmt arguments allowed

_{Ignore this finding from golang_fmt_errorf_no_params.}

[axelKingsley]

Reviewed offline, and then again synchronously with @protolambda . I addressed the minor bits I saw myself.