fix: add schema validation for stamps

[kyranjamie]

Try out Leather build 23e1dbf — Extension build, Test report, Storybook, Chromatic

Following the outage last night, caused by a schema change on the Stamps API, it's important we add thorough validation to API responses to prevent this happening again.

Here, I've added them for Stamps. On validation fail, we trigger an analytics event, which we could set alerts for.

I've used Zod, which is a library change we haven't discussed, but it's better at inferring types, more widely adopted for React apps, and we can use in mobile app, rather than continuing with Yup. LMK if anyone disagrees with this move to replace Yup.

I'll open issues for us to validate responses, and infer types, from other APIs as well.

[edgarkhanzadian]

I've used fp-ts and io-ts a lot before. It is a more opinionated version of a zod. It was very convenient to easily:

1. handle errors of mismatches coming from the backend side
2. pinpoint a bug and rollout a quick fix for it.

anyway, 2 hands up for zod 🙌. But can we open this PR in monorepo? This query is already moved to there in this PR leather-io/mono#113

[pete-watters]

👍 Maybe this is a pattern we can apply to a generic query wrapper?

[fbwoolf]

Looks good, thx for doing. 👍

[kyranjamie]

@edgarkhanzadian I will push a commit to your PR

[kyranjamie]

Merging in for now, but to refactor once Edgar's PR is merged into mono

[reinamora137]

fyi this is the current schema at stampchain:

interface StampRow {
  stamp: number | null;
  block_index: number;
  cpid: string;
  creator: string;
  divisible: number;
  keyburn: number | null;
  locked: number;
  stamp_base64: string;
  stamp_mimetype: string;
  stamp_url: string;
  supply: number;
  timestamp: Date;
  tx_hash: string;
  tx_index: number;
  ident: SUBPROTOCOLS;
  creator_name: string | null;
  stamp_hash: string;
  is_btc_stamp: number;
  file_hash: string;
}

type SUBPROTOCOLS = "STAMP" | "SRC-20" | "SRC-721";