indexer: Update DB package

[mslipper]

Updates the indexer's DB package to support both Bedrock and the legacy system. 90% of of this is a revert back to Mark's last commit on the indexer pre-Bedrock.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d2180a2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mslipper]

Current dependencies on/for this PR:

• develop
  • PR indexer: Restore some bindings #3658
    • PR indexer: Update DB package #3659 👈

This comment was auto-generated by Graphite.

[mergify]

This PR changes implementation code, but doesn't include a changeset. Did you forget to add one?

[semgrep-app]

Semgrep found 10 unchecked-type-assertion findings:

• indexer/bindings/legacy/scc/statecommitmentchain.go: L230, L261, L292, L323, L354, L385, L416, L447, L478, L509

Unchecked type assertion.

_{Created by unchecked-type-assertion.}

[tynes]

Is the plan to test this using the op-e2e utils once we get more stuff cleaned up?

There are currently linting errors, will review again once fixed

[mslipper]

Correct, the last PR in the chain will have op-e2e tests. I’ll fix the linter.

[roninjin10]

Approving assuming checks pass

[tynes]

Correct, the last PR in the chain will have op-e2e tests. I’ll fix the linter.

I'm realizing there isn't a good way to include legacy contracts in op-e2e, is this something you would like to do?

[mergify]

Hey @mslipper! This PR has merge conflicts. Please fix them before continuing review.

[mslipper]

I'm realizing there isn't a good way to include legacy contracts in op-e2e, is this something you would like to do?

I don't think we need to - they're already in bindings, and I can use a real network to test legacy support for the indexer.