Prefer patch-package approach instead of module augmentation?

[dotansimha]

We can PR libraries to add support, and create a patch file from the dist output of those libraries. This way it can be used without module augmentation, and solve issues like #15

I started to create PRs for libraries to support this built-in:

• feature: added support for automatic type inference with typed-document-node apollographql/apollo-client#6720

Thoughts:

• patch-package needs to support patches from npm module (should be able to do that with --patch-dir flag), or from a url (which isn't supported at the moment, according to the issues)
• Simplify the setup of this package, get rid of support packages, and ship patches as part of the core library? 🤔

[dotansimha]

Done in #26