Add ChainExportRange API method

[travisperson]

Checklist

• This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
• I have a specific, actionable, and well motivated improvement to propose.

Lotus component

• lotus daemon - chain sync
• lotus miner - mining and block production
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt)
• lotus miner/market - storage deal
• lotus miner/market - retrieval deal
• lotus miner/market - data transfer
• lotus client
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Improvement Suggestion

The ChainExport command doesn't provide an accurate way to export a segment of the lotus chain.

For archival and testing purposes it would be beneficial to be able to export an exact range of tipsets by adding a new method ChainExportRange that accepted two TipSetKey values as arguments and does not enforce a minimum epoch height between them (eg a call with both arguments the same should export a single TipSet).

The ChainExportRange should also accept a set of options

• Include Messages
• Include Message Receipts

It will be important to think through the exact inclusiveness of the method to ensure that no data is missed under the following usage:

ChainExportRange(ChainGetTipSetByHeight(a), ChainGetTipSetByHeight(b))
ChainExportRange(ChainGetTipSetByHeight(b), ChainGetTipSetByHeight(c))

I think ChainGetTipSetByHeight is the correct method to use here, I think as long as it's consistent it should be fine

The above should include the same data as

ChainExportRange(ChainGetTipSetByHeight(a), ChainGetTipSetByHeight(c))

Additionally a command should be added to lotus-shed to support the usage of this API method, mostly because chain export enforces a minimum epochs to export.

The export should construct CARv2 files with the index.

[travisperson]

If we want to go crazy we could also add options to make including state and blockheaders optional as well, which would allow this method to be used to extract just the messages. However, ChainGetMessagesInTipset already exists and can be used to grab this data and pack a car file manually.

[travisperson]

With support of message receipts this will close out #3849

[travisperson]

This export should allow for exporting of CARv2 files with the index.