fix(store/v1): Do not panic on prune in Commit

[itsdevbear]

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
• confirmed ! in 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
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• updated the relevant documentation or specification, including comments for documenting Go code
• 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 all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[alexanderbez]

nit: changelog

[tac0turtle]

we need to make sure this lands on main, also what are the implications here? would we prune later on or never @cool-develope

[alexanderbez]

The core implication is that pruning execution does NOT impact consensus. So for example something borked in pruning (e.g. disk IO failure or logic failure), we don't want that to impact consensus as it's unrelated.

In store v2, we'd return an error here. But for <= 0.50, we should avoid the panic.

[tac0turtle]

nvm we dont have to get this on main, only need to tag 1.0.1, ill add the changelog