feat: add local snapshots management commands (backport #16067)

[mergify]

This is an automatic backport of pull request #16067 done by Mergify.
Cherry-pick of c1ceb3b has failed:

On branch mergify/bp/release/v0.46.x/pr-16067
Your branch is up to date with 'origin/release/v0.46.x'.

You are currently cherry-picking commit c1ceb3bdd.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.md
	new file:   client/snapshot/cmd.go
	new file:   client/snapshot/delete.go
	new file:   client/snapshot/dump.go
	new file:   client/snapshot/export.go
	new file:   client/snapshot/list.go
	new file:   client/snapshot/load.go
	new file:   client/snapshot/restore.go
	modified:   snapshots/manager.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	both modified:   server/types/app.go
	both modified:   server/util.go
	both modified:   simapp/simd/cmd/root.go
	deleted by us:   simapp/simd/cmd/root_v2.go
	both modified:   snapshots/store.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[tac0turtle]

not sure why ci is not running here? @julienrbrt any ideas?

[julienrbrt]

not sure why ci is not running here? @julienrbrt any ideas?

I think because of GH issues that happened at around the time of the last commit? I had to re-trigger a PR by submitting a commit yesterday because of that.