feat: Add fraudproof verification on a store level

Description

When a fraudproof is received by an optimint full node, it should first verify the fraudproof by doing a cross-reference of header app hash retrieved from the DA layer against inclusion proofs in the fraudproof on a store level.

Parts covered from the cycle of a fraudproof:

Optimint Full/Light Node (Verifier of fraudproof)

It verifies the fraudproof by doing a cross-reference of a header app hash from the blockchain against the contents of a fraudproof

This PR simulates this check in the baseapp module

Parent issue: #253

Builds on top of: #248

Closes: #253

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...

[x] included the correct type prefix in the PR title
[x] added ! to the type prefix if API or client breaking change
[x] targeted the correct branch (see PR Targeting)
[x] provided a link to the relevant issue or specification
[x] followed the guidelines for building modules
[x] 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)

celestiaorg / cosmos-sdk