Research Typescript as an alternative for testing

[NonlinearFruit]

(Idea came from #46)

Can we cleanly use Typescript just for testing?

[NonlinearFruit]

Typescript doesn't do runtime checking so it can't check if json matches a type.

• Typescript Type to Json Schema generator: https://github.com/YousefED/typescript-json-schema
• Validate Json Schema: https://github.com/tdegrunt/jsonschema

[NonlinearFruit]

Use describe.each() for parameterized test groups (source) or test.each. it is an alias for test

[NonlinearFruit]

The goal is to have more specific error messages when something is broken. Right now with our tests, it will say 'Something didn't meet this requirement' but doesn't always say which creed and where in the creed it failed.

If typescript vitests can do this, we should convert. There are other benefits but this is the primary one

[NonlinearFruit]

We have:

• parameterized tests (for the creeds in the creeds/ folder)
• schema verification (for metadata and creed specific schemas)
• ascii only verification

The footnote-y bits are left:

• has a footnote for each proof text
• has a proof text for each footnote
• has no footnotes in non-'WithProofs' strings

Maybe also test:

• footnote ids are consecutive (starting at 1)

[NonlinearFruit]

It works!! All 'em tests be re-written and it is pretty nice.

Here are some stretch goals:

• proof text ids are consecutive (starting at 1)
• json scheme generated from typescript type
• Isolate the typescript-y bits to the test directory
• break some of the larger tests into parameterized tests with descriptive names

[NonlinearFruit]

We're going to TypeScript!

#48