`list-messages` order should be sequential

[wjmelements]

Checklist

• 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 feature request to propose.

Lotus component

• lotus daemon - chain sync
• lotus fvm/fevm - Lotus FVM and FEVM interactions
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt/WinningPoSt)
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

It would be convenient for some tooling if the messages of ./lotus state list-messages --cids --from <> were sequentially ordered. From spot checking I think they have an ordering; I think they are in reverse block order and then ordered within the block. Without this I have to do extra steps to order them this way.

Describe the solution you'd like

I would like for list-messages --from to be ordered by nonce, which would also be the order they were executed.

Describe alternatives you've considered

It would also be acceptable for my use case if they were in reverse-order.

Additional context

No response

[rvagg]

Probably easiest to add a new flag in the cmd itself rather than digging around in the internal API call; the order is mostly defined by block order in tipset (it'll also group by signature type within a block for reasons) and that's pretty standard across the codebase.

lotus/cli/state.go

Line 819 in 190d781

var StateListMessagesCmd = &cli.Command{