typescript migration

[acao]

redo of #191 , with a graphql upgrade as well

• type: module so that we're using the latest and greatest in module resolution/etc
• jest -> vitest because jest doesn't support esm well
• vitest.config.ts contains an alias to use cjs graphql because graphql-relay doesn't publish a module bundle yet (otherwise tests have realm error)
• tweak tests because of changes in graphql 14 -> 16, and in upstream data source values (text where number strings are expected, etc)
• dynamic imports seemed to be the best approach for importing data
• drop babel because it's not needed for a server side application (previously swapi was entirely clientside, so it makes sense it was there before)
• switch from complex eslint setup to typescript eslint reccomended for simplicty
• add github action workflow
• replace dev scripts with netlify dev environment, which mocks the functions interface and models reverse proxy and redirect rules
• remove everything flow related, replace with typescript
• cache cache/data.json both in netlify and github actions for faster CI
• note: most of the net lines of change are reflected in package-lock.json

[acao]

@Urigo this doesn't make sense, I can't believe the type fidelity has fallen this much in graphql, migrating from flow to typescript it's even more apparent, I remember types in 14 at least had more inference, am I doing something incorrectly here?

[Urigo]

cc @dotansimha @n1ru4l @saihaj