warn when user try to use apollo-boost as an apollo-client

[quentin-]

👋,

It is a common mistake to use the apollo boost constructor as an Apollo client constructor

• https://twitter.com/stubailo/status/1004040418772697088
• https://stackoverflow.com/questions/50688998/using-apolloclient-with-node-js-fetch-is-not-found-globally-and-no-fetcher-pas
• Highlight the switch to apollo-client #3548

This PR prints a warning when initializing apollo boost with unsupported options.

Checklist:

• If this PR is a new feature,
• Make sure all of the significant new logic is covered by tests
• If this was a change that affects the external API

[hwillson]

Thanks for working on this @quentin-! I'm not super crazy about the idea of having to maintain PRESET_CONFIG_KEYS, when we already have the same details in the PresetConfig interface, but there isn't much we can do about this right now (and I totally get why you set it up like this - this isn't a knock against anything you've done! 🙂). I messed around with Typescript transforms a bit and ran into a world of hurt trying to get the transforms working with rollup properly. Given that Apollo Boost is going to disappear when Apollo Client 3 is released though, I think we should be okay here for now. Thanks again - LGTM!