breaking(nova-react-test-utils): add support for Relay

[sjwilczynski]

Joint work with @jakobkhansen

In scope of this PR we add support for using Relay client with the Nova decorator and add a feature of specifying query needed to be run and way to pass result of that query to the component rendered in Story. Check the documentation that we added in README for more details about the features.

Additionally we changed the structure of the package so that now users have access to same functions for both client but need to import from different paths. For example:

• to import Relay based utils one needs to do import { getNovaDecorator } from "@nova/react-test-utils" or import { getNovaDecorator } from "@nova/react-test-utils/relay"
• to import Apollo based utils one needs to do import { getNovaDecorator } from "@nova/react-test-utils/apollo"
  Same patterns applies for utilities for unit tests

To verify our work, we added more stories and tests in packages/examples now showcasing both GraphQL client variants

[ansemb]

I like having @nova/react-test-utils/apollo and @nova/react-test-utils/relay.

I wouldn't mind having the index.ts only for relay, hence have @nova/react-test-utils (relay) and @nova/react-test-utils/apollo as I think relay should be considered default going forward, though that might also feel weird.

[sjwilczynski]

@ansemb

I like having @nova/react-test-utils/apollo and @nova/react-test-utils/relay.
I wouldn't mind having the index.ts only for relay, hence have @nova/react-test-utils (relay) and @nova/react-test-utils/apollo as I think relay should be considered default going forward, though that might also feel weird.

This is how it works right now actually. Because we set the main field as ./lib/relay/index.ts when importing without subpath it will use relay version. I decided to keep both subpaths for consistency tough

[Markionium]

Forgot to complete this yesterday :)