fix: prevent double spends after upgrades for transfer channels

[colin-axner]

Description

Packet receipts are used to check if a packet has already been received on an unordered channel. After an upgrade, it's possible to resubmit a historical proof to allow an attacker to double spend.

A secondary fix will be needed to prevent double spends when upgrading from ordered to unordered. This will be discussed internally tomorrow

The pruning tests need to be cleaned up a little before merge (I didn't update all the tests)
closes: #XXXX

Commit Message / Changelog Entry

type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[colin-axner]

we will go with the solution outlined in #5651