Update subgraphs for m2 contract changes

[mooselumph]

Why are these changes needed?

Checks

• I've made sure the lint is passing in this PR.
• I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
• Testing Strategy
  • Unit tests
  • Integration tests
  • This PR is not tested :(

[jianoaix]

should we remove https://github.com/Layr-Labs/eigenda/blob/master/subgraphs/eigenda-operator-state/src/bls-pubkey-compendium.ts ?

[jianoaix]

What about the addresses of these new contracts?

[mooselumph]

These are dummy addresses that get replaced by the deployer. Making that explicit by zeroing them out.

It looks like the preprod-goerli and goerli ones may correspond to actual contracts on goerli, but we can't update those until the new deployment.

[jianoaix]

should we remove https://github.com/Layr-Labs/eigenda/blob/master/subgraphs/eigenda-operator-state/src/bls-pubkey-compendium.ts ?

Also:

• https://github.com/Layr-Labs/eigenda/blob/master/subgraphs/eigenda-operator-state/src/bls-registry-coordinator-with-indices.ts
• https://github.com/Layr-Labs/eigenda/blob/master/subgraphs/eigenda-operator-state/src/bls-pubkey-registry.ts