Support payment rate increase when a data set has `withIPFSIndexing`

[rvagg]

Similar to the FilCDN setup we have no for withCDN, but doesn't require an extra rail (for now at least, maybe there's a future where a rail goes to an IPNI entity). The service provider should be able to charge more for performing, publishing, and maintaining an index of multihashes in each piece in a data set.

The simplest way to approach this is to just work out a price per TiB that's roughly connected to the size of an index for "average" indexing data—which will be tricky to work out, but we'd need to land somewhere between the large-file IPFS case where you end up with 1MiB blocks and the small-chunk size of blockchain type IPLD data that fills up an SP's Yugabyte.

There's no obvious on-chain proof of service here, although perhaps we could get to some roll-up reporting of IPNI ingested data recorded on chain but that seems like a bigger technical problem for the future. For now, we'd have the ability of a user to terminate a service if their data doesn't show up where they expect it to.

[jennijuju]

as discussed in Colo - we will not add this in m3. in the future, we will upgrade the architecture of the system to abstract the features from pdp core, then services and/or features like warm storage, IPFSIndexing, can be easily deployed onto of pdp backed CIDs