Fix useRefetchable/fromData incompatibility

[benjamin-thomas]

Hello!

#628 introduced fromData, but it appeared to be incompatible with the useRefetchableFragment hook.

This change short-circuits the hook, similar to what was done in useFragment already.

For the background info: I encountered this error while trying to render some components on a "storybook-like" page.

The runtime error looked something like this:

    Invariant Violation: Relay: Expected to receive an object where `...TestRefetching_user` was spread, but the fragment reference was 
not found`. This is most likely the result of:                                                                                          
    - Forgetting to spread `TestRefetching_user` in `useRefetchableFragment()`'s parent's fragment.
    - Conditionally fetching `TestRefetching_user` but unconditionally passing useRefetchableFragment() prop to `TestRefetching_user`. I
...

The failing test captures the error I encountered faithfully

[tsnobip]

great fix @benjamin-thomas!

I'd just avoid using @obj and don't forget to update the CHANGELOG.md (add a # master section on top)

[tsnobip]

LGTM now!

[benjamin-thomas]

Just a heads up, I added another commit to handle the pagination hook.

Let's say you want to demonstrate a component that requires pagination, this resulted in a runtime error. I applied the same solution as before : detect if we have test data from fromData and NOOP, otherwise behave as before.

There's probably at least one or a few hooks that could receive the same treatment but I'm only concerned with those two at the moment.