feat: CLI: add claim-extend cli

[LexLuthr]

Related Issues

Fixes #10001

Proposed Changes

The new command creates extend message[s] based on the following conditions

1. Extend all claims for a miner ID
2. Extend all claims for multiple miner IDs
3. Extend specified claims for a miner ID
4. Extend specific claims for specific miner ID
5. Extend all claims for a miner ID with different client address (2 messages)
6. Extend all claims for multiple miner IDs with different client address (2 messages)
7. Extend specified claims for a miner ID with different client address (2 messages)
8. Extend specific claims for specific miner ID with different client address (2 messages)

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rvagg]

maybe hold off until we make it work: filecoin-project/go-state-types#254

[rvagg]

merged types changes in filecoin-project/go-state-types#254, @rjan90 I think probably a new rc from go-state-types that we can pull in to master and release/v1.26.0?

[rvagg]

This looks really nice, if it works as advertised. I like that it's asking for confirmation when needing to spend datacap.

Did you have a draft itest somewhere for this when you found that encoding discrepancy originally on ClaimExtensionRequest? I know this is really hard to test, but perhaps there's something minimal we could do at least?

[LexLuthr]

I was testing e2e in devnet but an itest sounds good. I can create one which quickly creates a claim and then extends it.

[beck-8]

Hello, I took the time to look at it today.

I found that there is no out of gas processing, I don't know if I missed it.

This message is the same as the renewal sector. When the number is large, a large amount of gas will be used, exceeding the block limit, so an error will be reported when renewing a large number of deals.

So please confirm whether there is batching logic. If not, you may need to add it.

ps: When I was renewing the deal, I found that it was already out of gas around 2000-3000

[LexLuthr]

@beck-8 You are right. There is no batching logic. I will add it to #11764 with another fix.