feat: type inference

[hanakannzashi]

Implement type inference, this is a simple minimal implementation, use 1:1 mapping of JS type, still remain many features to be added.

• Support Uint8Array and other typed arrays

• Support literal enums

  enum Status { 
    Pending = 'Pending',
    Fulfilled = 'Fulfilled',
    Rejected = 'Rejected',
  }

  There is a challenge that how to represent Rust enum with JavaScript

• Support tuple

[hanakannzashi]

Will be helpful if you guys have a look @r-near @hmtrent

[hanakannzashi]

Another question is should we distinguish between schemas that have same generic type. e.g. u8 and u16 are both BorshSchema<number>, should change to BorshSchema<number, 'u8'> and BorshSchema<number, 'u16'>?

[hmtrent]

I think #4 is probably on a closer track towards implementing type inference, which also currently is 1:1 with input/output type mappings. I agree that this is desirable.

Note that #4 has the TypeOf helper, which does what Infer is trying to do in this PR. In order for Infer to work properly, it will more or less need to look like the TypeOf type helper in that PR.

I'd recommend sticking with PR #4 instead of this one; are there any new features we should port over to that PR?

[r-near]

@hanakannzashi looks good - feel free to take a look at the implementation here - it's before I went crazy and rewrote the library. But this would essentially be the most minimal changes required to make sure everything's fully-typed and backwards-compatible (comments are excluded):

• https://github.com/nameskyteam/borsher/blob/489a2c31e3ee14e75cdb8fffe01274c5984ec5b7/src/schema.ts
• https://github.com/nameskyteam/borsher/blob/489a2c31e3ee14e75cdb8fffe01274c5984ec5b7/src/index.ts