Remove typebox Static<> type inference in favor of TypeScript

[austin-denoble]

Problem

We use typebox for runtime validation of arguments in the Node client. Currently, we're leveraging typebox's Static<typeof schema> utility for generating TypeScript types out of these runtime schemas.

We've noticed this doesn't play well with documentation generation, and there have been some bug reports regarding issues possibly related to typebox's generated types.

Solution

Instead of relying on the typebox utility, use our own TypeScript types which are manually aligned with existing schemas.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Infrastructure change (CI configs, etc)
• Non-code change (docs, etc)
• None of the above: (explain here)

Test Plan

These are all typing changes so there shouldn't be any client code affected by these changes.

Make sure to run:
npm run lint

[jhamon]

I've never seen the | used on the first entry like this. Is that correct/valid syntax?

[austin-denoble]

This was a prettier addition, but yeah seems like valid syntax. I did have to look it up though, found this: prettier/prettier#6299