proofs: remove reliance on comet for proof system

### Summary
currently our proof system is tightly coupled with comet's light client verification system and types. The light client verification system isnt the best interface and may not be needed at all, instead we should define our own types for proofs, could be the same as now, but not pass it to comet like we do now. Out of process applications dont have this coupling. Im not sure why it exists in the sdk in the first place

### Problem Definition
application proof system is tightly coupled with comet.

### Proposal
Remove the coupling of the proof system in the code from the light client system in comet. We will need to talk to relayers, as this may effect them the most.