V2: Fix client side proving bug due to malformed G2 ingestion

[ethenotethan]

V2 supports both disperser/client side commitment generation. I.e a user can either:

1. Have the disperser generate the respective polynomial commitments for some blob to give to client who injects values into blob header OR
2. Have the client use their own kzg prover to generate the commitments and inject into blob header without relying on disperser

Currently for 2, there's a bug with referencing G2 when generating a kzg length commitment:

5125ms           role=eigenda_proxy
INFO [01-31|00:26:42.409]     Reading G2 points (33554432 bytes) takes 6.355542ms role=eigenda_proxy
INFO [01-31|00:26:42.409] Unmarshalling error: invalid fp.Element encoding role=eigenda_proxy
INFO [01-31|00:26:42.409] Unmarshalling error: invalid fp.Element encoding role=eigenda_proxy
INFO [01-31|00:26:42.409] Unmarshalling error: invalid fp.Element encoding role=eigenda_proxy
INFO [01-31|00:26:42.409] Unmarshalling error: invalid fp.Element encoding role=eigenda_proxy
CRIT [01-31|00:26:42.409] Application failed                       role=eigenda_proxy message="failed to create store: failed to create verifier: failed to create kzg verifier: failed to read 524288 G2 points from resources/g2.point: invalid fp.Element encoding"

I've fed necessary SRS context but this seems to be specific to how the eigenda parameterized prover works.