chore: small snapshot commands & docs improvement

[julienrbrt]

Description

Small improvements for the snapshots commands.
ref: #16248, #16249

Tested v0.46.13, with a Stride node (for #16248), with the only issue that I cannot export a snapshot of a state-synced node (first state sync from p2p, dump snapshots, go further in height, try to export it and then the following).

$ ./build/strided snapshots export
Exporting snapshot for height 3931257
Error: failed to generate snapshot chunk 0: iavl export failed for version 3931257: version does not exist

It does not work because this is nil: https://github.com/cosmos/iavl/blob/7afdfcd69dc956facacd4977c6658f3107f5db33/mutable_tree.go#L778
If I comment it out, it is then working fine. As this code has been there for a long time, I assume it is correct, but gladly have someone double check if that command is then working as intended (cc @yihuang / @cool-develope).
I am trying with this https://notional.ventures/resources/snapshots/stride now.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[yihuang]

If I comment it out, it is then working fine. As this code has been there for a long time, I assume it is correct, but gladly have someone double check if that command is then working as intended (cc @yihuang / @cool-develope).

is it possibly the goleveldb thing? I've seen this before, and seems fixed by reverting the goleveldb version.

[julienrbrt]

If I comment it out, it is then working fine. As this code has been there for a long time, I assume it is correct, but gladly have someone double check if that command is then working as intended (cc @yihuang / @cool-develope).

is it possibly the goleveldb thing? I've seen this before, and seems fixed by reverting the goleveldb version.

Yep, that was that. Added that in the release notes:7e78427.