Handle aliases in graphql-flow.

[jeresig]

Summary:

This adds a new option to the config for graphql-flow so that you can specify aliases to map to, to help resolve imports. I used the same format as Vite to keep things simple. This will make it so that we can support our ~/-style imports.

In the process I realized a number of things about this repo were broken, so I fixed them:

• We weren't running tsc, so I fixed that, and then fixed a bunch of TS failures that were hidden.
• The ESLint config was broken, so I fixed that (and then fixed all the failures that came up).
• Prettier was broken (still expecting Flow), so I fixed that.
• VS Code wasn't set up properly, so I fixed that.
• The Github PR Workflow was broken, still expecting Flow/.js files, so I fixed that.

Hopefully this helps things to run more smoothly!

Issue: FEI-5745

Test plan:

I ran yarn tsc and yarn eslint src/**/*.ts and they both passed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 89cfb22

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@khanacademy/graphql-flow	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[jeresig]

This is the new change.

[jeresig]

This is the test confirming that it works.

[jeresig]

This is the format of the new alias config setting.

[kevinb-khan]

LGTM. Did we only recently run into issues with graphql-flow having troubles traversing ~/ style imports?

Thanks for fixing all of the tooling in this repo. Sorry for missing that during the TypeScript upgrade.

[jeresig]

@kevinb-khan So it turns out that I hit this during: https://github.com/Khan/webapp/pull/23926 we were hitting issues where we were importing GraphQL fragments across packages using a ~/ prefix. Before this point there hadn't been any cases of this, but once I started using ~/ everywhere this code started to break.