chore: rename snapshot proto package

[julienrbrt]

Description

See #14591 (comment)
As per #14597 (comment) this PR renames the package to v1 but not re-add the fields compared to #14608 (on release/v0.47.x)

---

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)

[julienrbrt]

One thing actually, we've changed the package name in 0.48 vs <= 0.47 (3222be3).
So it will be proto breaking anyway in v0.48 I think.

[amaury1093]

One thing actually, we've changed the package name in 0.48 vs <= 0.47 (3222be3).
So it will be proto breaking anyway in v0.48 I think.

Oh, if we changed package names, then we can remove fields freely in the newly-named package. It's not actually a rename, but basically leaving the old one cosmos.base.snapshots.v1beta1 as-is (it's on buf anyways), and creating a new one cosmos.base.store.snapshots.v1beta1. So we're free to do anything in the new one.

Also, maybe we can use v1 for the new one?

[julienrbrt]

One thing actually, we've changed the package name in 0.48 vs <= 0.47 (3222be3).
So it will be proto breaking anyway in v0.48 I think.

Oh, if we changed package names, then we can remove fields freely in the newly-named package. It's not actually a rename, but basically leaving the old one cosmos.base.snapshots.v1beta1 as-is (it's on buf anyways), and creating a new one cosmos.base.store.snapshots.v1beta1. So we're free to do anything in the new one.

Also, maybe we can use v1 for the new one?

Okay, so I am not re-adding it here, but only rename it to v1 and in v0.47 (where it is not yet renamed, I can add it as deprecated if that is what is wanted)

[julienrbrt]

We had no changelog for the package moving (I am noticing that we mostly forgot to add a changelog for all store refactors). Precising the renaming as well.

[tac0turtle]

do we want to keep the old one around?

[julienrbrt]

do we want to keep the old one around?

Don't think it's necessary as it isn't used.