feat: curio: allow multiple pieces per sector

[LexLuthr]

Related Issues

Proposed Changes

1. Multiple piece per sector in market and precommit
2. All open sectors are coordinated from DB
3. Config changes for MaxDealWaitTime
4. DDO deals in market
5. DDO deals in precommit
6. Updated backpressure
7. Seal command

• Test multiple deals in devnet
• Test seal command
• Test Curio restart with Open Deal sectors
• Test Boost restarts while AP()
• Test Curio restarts while AP()
• Test DDO deal
• Happy path test without deals

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

[LexLuthr]

@snadrus This is WIP, I will be moving everything to DB.

[LexLuthr]

Converting back to draft as I need to add new tables to avoid sectors_sdr_initial_pieces_sp_id_fkey and do the relevant code changes. I will also try to account for snap-deals.

[magik6k]

This is an absolutely amazing chunk of work!

Some easy to address comments, but nothing fundamentally wrong. My main concert is around how we assign pieces to sectors - where we should be taking TermMin/Max bounds of the piece we're inserting vs expirations of pieces already assigned to a given sector (also possible that I've missed this bit of logic, this PR is big).

In lotus-miner this is done in - https://github.com/filecoin-project/lotus/blob/master/storage/pipeline/sealing.go#L155

[github-actions]

All checks have passed

[magik6k]

Looks good, as much as it is possible to review PRs this big.

We'll probably find some issues here when we start running this code, so the sooner we do that the better.