feat: verify inclusion proofs

[tomyrd]

closes #485

This PR adds verification for inclusion proofs on every sync. The status of the proof (Valid, Invalid or Not verified) is stored in a new field inside InputNoteRecord.

In terms of functionality, all proofs are asumed to be NotVerified unless it comes directly from the node. On every sync, all committed notes that aren't verified get updated with a new status. If a note is set to be invalid, it's not eliminated from the client but it is no longer shown.

[bobbinth]

Thank you! Not a review - just a couple of preliminary comments:

If a note is set to be invalid, it's not eliminated from the client but it is no longer shown.

I'm not sure we should hide such notes form the user - it may be unclear why some notes have disappeared. Instead we should probably still show them to the user but clearly indicate that these notes have invalid proofs. Then, it would be up to the user to either delete the notes or do something else (e.g., try to retrieve proof by note ID). These additional things could be done in separate PRs.

More generally though, i wonder if we should first map out note states and transitions more comprehensively as I mentioned in #487 (comment). This may inform how exactly we may want to address different state transitions.