feat: sealing: Use bitfields to manage sector numbers

[magik6k]

Related Issues

Needed for SaaS

Proposed Changes

• Move sector number assigning logic to use stored bitfields instead of stored counters
• Make it possible to reserve ranges of sector numbers
  • Using lotus-miner sectors numbers reserve/free cli or SectorNumReserve/Free API.
• Add a command which makes it possible to see the sector assigner state - lotus-miner sectors numbers info
• Add a command which makes it possible to view sector number reservations - lotus-miner sectors numbers reservations

Some cli examples:

$ lotus-miner sectors numbers info
Next free: 4
Allocated: 0-3,11-12
Reserved: 0

$ lotus-miner sectors pledge
Created CC sector:  4

$ lotus-miner sectors numbers info
Next free: 5
Allocated: 0-4,11-12
Reserved: 0

$ lotus-miner sectors numbers reserve test-res 5-9

$ lotus-miner sectors numbers reservations
reservations: 1
test-res: count=5 5-9

$ lotus-miner sectors numbers info
Next free: 10
Allocated: 0-4,11-12
Reserved: 5-9

$ lotus-miner sectors pledge
Created CC sector:  10

## sectors 11/12 were already allocated for whatever reason, so the assigner will assign 13, which is the next available number

$ lotus-miner sectors numbers info
Next free: 13
Allocated: 0-4,10-12
Reserved: 5-9

$ lotus-miner sectors pledge
Created CC sector:  13

## if we drop the reservation without any sector numbers in that being used, the assigner will now try to reuse those numbers to reduce number gaps

$ lotus-miner sectors numbers free test-res
$ lotus-miner sectors numbers info
Next free: 5
Allocated: 0-4,10-13
Reserved: 0

$ lotus-miner sectors pledge
Created CC sector:  5

TODO

• Make sealing pipeline use bitfields instad of a stored sector counter for tracking sector number assignments
  • Backwards compatible with the old stored counter so upgrading/downgrading lotus-miner is free of manual migrations
• Add commands/utils to allocate / reserve blocks of sector numbers
  • Makes it possible for SaaS to make sure lotus won't use specified ranges of sector numbers
• Make sector number allocation logic look at miner-actor state to not create sectors with numbers which are marked as allocated
• Describe how to use here
• Test all this
  • Itests
  • Manual testing

Checklist

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

• All commits have a clear commit message.
• The 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, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, test
  • area: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps
• This PR has tests for new functionality or change in behaviour
• If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in https://lotus.filecoin.io or Discussion Tutorials.
• CI is green