Allow startPolling in useLazyQuery without having to exec first

[masad-frost]

Checklist:

• If this PR is a new feature, please 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
• If this was a change that affects the external API used in GitHunt-React, update GitHunt-React and post a link to the PR in the discussion.

Related to apollographql/apollo-client#5140

This is a proof of concept / draft

When using useLazyQuery, the return value does not include ObservableQueryFields, hence you cannot call startPolling until after you call runLazyQuery which is inconvenient.

At the very least the type of the return value of useLazyQuery should be modified to indicate that ObservableQueryFields maybe undefined.

[apollo-cla]

@masad-frost: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[masad-frost]

Also wondering why lazy queries weren't just a convenience for switching skip from true to false and then forceUpdateing, wouldn't that simplify the internals?

[masad-frost]

@hwillson Looks like you were interested in looking at the problem in apollographql/apollo-client#5140

This PR explains why this is happening and adds a POC for a solution, lazy queries lose most of their value because of this issue

[masad-frost]

Any body looks at PR's here? :/