feat: switch build to TS + all tests :tada:

[golota60]

above and beyonce

things done:

• switched out build to use ACTUAL TS TYPES(this adjusts types so next release will be slightly breaking. would appreciate if you checked the branch out and compared old&new build artifacts(i did and it looks :ok_hand: but would appreciate a second opinion to be sure)
• remove old types
• converted all tests to TS(should prolly also switch out enzyme)
• bootstraps TS example from types/ and adds it to example dir

[jquense]

Damn man this awesome.

[golota60]

i've taken a better glance at build differences - all seem to be related to code-splitting, here they are(left is old right is new)

1. package.json slight differences(non-issue imo)
2. minifying differences(non-issue imo)
3. TS declaration file changes - declaration file changes. they just differ cause they're not static declaration files, but are generated by TS. We didn't remove any types, they are just not so neatly packed together as they were previously, they are just a little bit more over the place(will try to fix that in the coming days by moving stuff from typeUtils.ts to files themselves, instead of a one big file)
4. server.tsx missing(this just seems random, think it happened cause stuff wasn't explicitly exported - fixed that in newest commit).

So yeah, i think merging this probably won't introduce anything wrong, but since it's a whole switch from JS->TS i expect that some slight issues might come up i've used meld to compare the changes.

Overall I'd say this is ready to be merged(like I said, I expect issues to be small to nonexistent with this), although I'd understand if we want to turn this into a feature branch or something. I'd say we should face it head on and merge this and then deal with any issues while releasing :smile: but that's just me