Register as a provider for stored CIDs to the network

[aarshkshah1992]

Retrieval by any Cid(and not just the root Cid) from a single Storage Deal/Piece.

• Build a top level (cid -> PieceCid) Index in the DAGStore using go-indexer-core.
  WIP PR at Inverted Index dagstore#99.
• Markets and Lotus changes to allow retrieval by any Cid.
  WIP PR at retrieve by any CID (not just root CID) and reference provider integration #629 AND
  feat: markets: Integrate index ingest protocol and retrieve by any CID lotus#7313.
• Build CLI support for:
  - [ ] Miners to lookup the PieceCids that contain a given Cid.
  - [ ] Miners to inspect the space taken up by the top-level Index.
• Smoke Test on Sofia Miner.

Miner announces all cids it can serve retrievals for to the Network Indexer.

• Integrate chore(deps): use go-car master version #639. (nice to have)
• CARv2 dep upgrade to allow iterable CAR Indices.
• Miner makes Index announcements for all storage deals and also serves those Indices to the network Indexer. This is currently blocked on the reference provider being built by Data-systems. ETA September last week.
• Build CLI support for:
  - [ ] Force an Index announcement for an existing storage deal to the network Indexer.

Required Migration/s

• Miners will have to re-run the DAGStore shard migration they ran for M1 from scratch again. The reason is that the CARv2 lib now has a "breaking change" to the Index format to allow the Index to be iterable. The Index needs to be iterable so Miner can announce it's local Cid indices to the network Indexer.

• We can piggy-back the "migration" of building the top-level Index in the DagStore and making announcements for them to the network Indexer on top of the above mentioned DAGStore shard migration. We should therefore do only one release for the entire M2 Ignite work so as to make life easy for users by not having them do multiple migrations.

[aarshkshah1992]

cc @jacobheun @jennijuju for tracking/concerns.