Add --unproven flag to the sectors list command

[magik6k]

Depends on #7261

This PR adds an --unproven flag to lotus-miner sectors list, which makes it print only sectors which are being sealed. It also is a lot faster than printing all sectors.

[codecov]

Codecov Report

Merging #7263 (271cbf9) into feat/sectors-list-sealing-deals (3451964) will increase coverage by 0.02%.
The diff coverage is 18.75%.

@@                         Coverage Diff                         @@
##           feat/sectors-list-sealing-deals    #7263      +/-   ##
===================================================================
+ Coverage                            39.07%   39.09%   +0.02%     
===================================================================
  Files                                  614      614              
  Lines                                64912    64920       +8     
===================================================================
+ Hits                                 25366    25383      +17     
+ Misses                               35140    35139       -1     
+ Partials                              4406     4398       -8     

Impacted Files	Coverage Δ
cmd/lotus-miner/sectors.go	11.13% <18.75%> (-0.09%)	⬇️
chain/actors/builtin/miner/diff.go	48.52% <0.00%> (-10.30%)	⬇️
chain/stmgr/call.go	67.87% <0.00%> (-3.64%)	⬇️
extern/sector-storage/sched.go	83.05% <0.00%> (-1.66%)	⬇️
extern/storage-sealing/fsm.go	57.42% <0.00%> (-1.61%)	⬇️
chain/vm/vm.go	59.47% <0.00%> (-1.12%)	⬇️
chain/messagepool/selection.go	80.12% <0.00%> (-0.41%)	⬇️
node/impl/storminer.go	22.46% <0.00%> (-0.40%)	⬇️
chain/sync.go	64.94% <0.00%> (-0.34%)	⬇️
chain/messagepool/messagepool.go	57.00% <0.00%> (-0.13%)	⬇️
... and 15 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3451964...271cbf9. Read the comment docs.

[ZenGround0]

One minor point of confusion that I think is possible with this code and terminology is that there is a brief window where the sector is marked in onchain data as "unproven" but the sealing FSM sees the sector as "Proving". If I understand the FSM correctly the sector transitions to FinalizeSector and then Proving after successful ProveCommit message without waiting for any window posts but miner state keeps the sector in "unproven" state until first post.

If there is another name you could give this flag (unfinalized, uncommitted, unporeped?) it would prevent confusion with the on chain concept.