Allow useLazyQuery trigger fn to change query

[phryneas]

fixes #10496

Locally, many of the tests were erroring out for me - but independently of the useLazyQuery tests and even without my changes. So let's see what CI has to say about this.

Checklist:

• If this PR contains changes to the library itself (not necessary for e.g. docs updates), please include a changeset (see CONTRIBUTING.md)
• 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

[changeset-bot]

🦋 Changeset detected

Latest commit: ac72e11

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@apollo/client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[phryneas]

This was necessary since LazyQueryHookOptions does not 100% match any member of OptionsUnion and this way it felt cleaner than adding LazyQueryHookOptions to the union (which is in the shared utilities folder and has no direct relation to the React hooks). This actually fixes a few things where before, mergeOptions would return a OptionsUnion instead of the correct type.

[alessbell]

Locally, many of the tests were erroring out for me - but independently of the useLazyQuery tests and even without my changes. So let's see what CI has to say about this.

We've pushed a few things to improve the reliability of our test suite recently that have helped, but unfortunately a flaky test still failed here, along with the bundlesize check which seems to be narrowly above the limit (feel free to increase it in bundlesize.ts).

I suspect that on the next CI run this will be 🍏

[phryneas]

Yup, now it's green 🎉

[alessbell]

🚀

[jerelmiller]

Nice! I had one minor nit for the changelog verbage, but otherwise this looks great. Welcome to the team 🎉 🎉 🎉