feat: add local snapshots management commands

[yihuang]

Closes: #16066

Manage local snapshots

Usage:
  simd snapshots [command]

Available Commands:
  delete      Delete a local snapshot
  dump        Dump the snapshot as portable archive format
  export      Export app state to snapshot store
  list        List local snapshots
  load        Load a snapshot archive file into snapshot store
  restore     Restore app state from local snapshot

Flags:
  -h, --help   help for snapshots

Global Flags:
      --home string         directory for config and data (default "/Users/yihuang/.simapp")
      --log_format string   The logging format (json|plain) (default "plain")
      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
      --trace               print out full stack trace on errors

Use "simd snapshots [command] --help" for more information about a command.

Description

Closes: #XXXX

---

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)

[github-actions]

Change potentially affects state.

Call sequence:

(*cosmossdk.io/store/snapshots.Manager).sortedExtensionNames (store/snapshots/manager.go:422)
(*cosmossdk.io/store/snapshots.Manager).createSnapshot (store/snapshots/manager.go:192)
(*cosmossdk.io/store/snapshots.Manager).Create (store/snapshots/manager.go:161)
(*cosmossdk.io/store/snapshots.Manager).snapshot (store/snapshots/manager.go:460)
(*cosmossdk.io/store/snapshots.Manager).SnapshotIfApplicable (store/snapshots/manager.go:444)
(*github.com/cosmos/cosmos-sdk/baseapp.BaseApp).Commit (store/snapshots/manager.go:458)

[julienrbrt]

nice! utACK.

[yihuang]

I'll add another command to make portable snapshots, basically bundle the Snapshot message together with the chunk files, which can be exchanged outside of the p2p network.

[tac0turtle]

utACK

[yihuang]

More complete now:

$ ./build/simd snapshots --help
WARNING: proto: file "google/protobuf/any.proto" already registered
Manage local snapshots

Usage:
  simd snapshots [command]

Available Commands:
  delete      Delete a local snapshot
  dump        Dump the snapshot for portable archive format
  list        List snapshots
  load        Load a snapshot archive file into snapshot store
  restore     Restore app state from local snapshot

Flags:
  -h, --help   help for snapshots

Global Flags:
      --home string         directory for config and data (default "/Users/yihuang/.simapp")
      --log_format string   The logging format (json|plain) (default "plain")
      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
      --trace               print out full stack trace on errors

Use "simd snapshots [command] --help" for more information about a command.

Example for dump/load:

$ ./build/simd snapshots dump 8190000 2 --home /tmp/test1 --output /tmp/arhive-8190000-2.tar.gz
$ ./build/simd snapshots load /tmp/arhive-8190000-2.tar.gz --home /tmp/test2
$ ./build/simd snapshots list --home /tmp/test2
height: 8190000 format: 2 chunks: 270

[tac0turtle]

lets fix the linting then we are good to merge

[chillyvee]

@yihuang - very useful

1. Any plans to backport to earlier cosmos-sdk versions? Should we try to assist?
2. Which testnet/mainnet chain did you test this code against? (if any)

[yihuang]

@yihuang - very useful

1. Any plans to backport to earlier cosmos-sdk versions? Should we try to assist?

2. Which testnet/mainnet chain did you test this code against? (if any)

Has back-ported to 0.47 0.46, we plan to release later

[holyxiaoxin]

My nodes are too bloated and they stopped producing snapshots, and I found these snapshots management commands hoping that I could export a node's snapshot and restore this snapshot into a newly init chain on another node.

@yihuang What is the workflow to restore the snapshot from a portable archive? I ran appd snapshots export to export latest state to snapshot store. Then ran appd snapshots dump <height> 3 to dump archive file. Then on a newly app init node with cofigurations set properly, with chain's config/genesis.json (state-syncable), I ran appd snapshots load height-3.tar.gz. Then ran appd snapshots restore 5 3 to restore chain state to snapshot. But after starting the chain, I received the following error:

panic: state.AppHash does not match AppHash after replay. Got
38C37A1E4FD2D3376663C6C87CD91660F7E5B432BBDDDB97939776D43489B510, expected .
State: {{{11 0} 0.37.2} app 1 0 :0:000000000000 2024-04-18 05:45:49.278222786 +0000 UTC ValidatorSet{
  Proposer: nil-Validator
  Validators:
    
} ValidatorSet{
  Proposer: nil-Validator
  Validators:
    
} ValidatorSet{
  Proposer: nil-Validator
  Validators:
    
} 1 {{22020096 -1} {100000 48h0m0s 1048576} {[ed25519]} {0}} 1 [] []}

Did you reset CometBFT without resetting your application's data? [recovered]
	panic: state.AppHash does not match AppHash after replay. Got
38C37A1E4FD2D3376663C6C87CD91660F7E5B432BBDDDB97939776D43489B510, expected .

Did you reset CometBFT without resetting your application's data?

I've also tried removing all the db folders before restoring, but got the same error.

When trying to do a snapshot statesync, I received the following error when starting the chain:

ERR failed to restore snapshot err="multistore restore: import failed: found database at version 56746000, must be 0" module=server
ERR State sync failed err="state sync aborted" module=statesync server=node