Fix issue with usage in TypeScript projects caused by 'compose' re-export

[larixer]

Fixes #279

As suggested by @migueloller compose is re-exported from redux instead of recompose, since implementation is completely the same, that's why we can drop depending on recompose completely.

TODO:

• If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change
• If this was a change that affects the external API, update the docs and post a link to the PR in the discussion

[migueloller]

Update the comment to say redux instead of recompose?

[larixer]

Thank you! Done

[migueloller]

Would it make sense to rebase so that the commit that removes the recompose dependency also imports from redux? This way the commit makes a non-breaking atomic change and can easily be reverted if necessary.

EDIT: This won't matter if the PR is squashed.

[larixer]

Sure. I will try now. I never did this before.... Any pointers appreciated

[larixer]

Okay, rebased everything into single commit

[jbaxleyiii]

@Vlasenko this is great, my only concern is with importing all of redux. This probably isn't an issue since apollo-client imports redux. Technically this integration doesn't actually rely on redux at all.

That being said, I'm great with this for now! Thanks for the PR