Fix swagger doc gen to resolve v2.BlobHeader

[pschork]

Swagger was including the (v1) core.BlobHeader instead of the v2.BlobHeader in the v2.BlobFeedResponse

v2.BlobFeedResponse{
blobs	[v2.BlobInfo{
blob_key	[...]
blob_metadata	v2.BlobMetadata{
blobHeader	core.BlobHeader{
accountID	[...] <-- accountID is inside the BlobHeader object

Checks

• 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.
• I've checked the new test coverage and the coverage percentage didn't drop.
• Testing Strategy
  • Unit tests
  • Integration tests
  • This PR is not tested :(

[jianoaix]

ah, this is not just a doc issue, it's a real bug. Our test seems weak.

[pschork]

Not sure. The go compiler does the right thing with core "github.com/Layr-Labs/eigenda/core/v2". I think swagger builds a naive package lookup so resolves to v1 core.BlobHeader