prevent accidental widening of inferred TData and TVariables generics for query hook option arguments

[phryneas]

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

This issue came up in a discussion with @benjamn about type behavior.
The PR is best explained by the comment I added on types.ts:

apollo-client/src/react/types/types.ts

Lines 311 to 335 in 3b538fb

	/**
	Helper type that allows using a type in a way that cannot be "widened" by inference on the value it is used on.
	This type was first suggested [in this Github discussion](https://github.com/microsoft/TypeScript/issues/14829#issuecomment-504042546).
	Example usage:
	```ts
	export function useQuery<
	TData = any,
	TVariables extends OperationVariables = OperationVariables,
	>(
	query: DocumentNode | TypedDocumentNode<TData, TVariables>,
	options: QueryHookOptions<NoInfer<TData>, NoInfer<TVariables>> = Object.create(null),
	)
	```
	In this case, `TData` and `TVariables` should be inferred from `query`, but never widened from something in `options`.
	So, in this code example:
	```ts
	declare const typedNode: TypedDocumentNode<{ foo: string}, { bar: number }>
	const { variables } = useQuery(typedNode, { variables: { bar: 4, nonExistingVariable: "string" } });
	```
	Without the use of `NoInfer`, `variables` would now be of the type `{ bar: number, nonExistingVariable: "string" }`.
	With `NoInfer`, it will instead give an error on `nonExistingVariable`.
	*/

[changeset-bot]

🦋 Changeset detected

Latest commit: 9315a76

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	Minor

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]

PS: this also fixes the incorrect type behaviour I demonstrated in this playground - although that should not be a problem going forward, since we want to remove the query option anyways.

[benjamn]

We've talked this over on Zoom/Slack and I agree it's an improvement.

If there are any reports of unexpected type errors on the release-3.8 branch, we can fix them before release.