[typescript-operations] No optional Result fields, unless deferred or conditional

[eddeee888]

Description

Fix Result fields being optional. In normal use cases, a requested field cannot be optional, just null.
There are some cases where a field can be optional:

• When it is deferred
• When it is conditional (with @skip or @include)

This PR fixes the issue by removing all related avoidOptionals for standard Result fields scenarios.
This makes it tighter and avoids the issue where users arbitrarily configure the result, which can lead to foot-gun situations

Related #10496

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

• Unit tests
• Integration tests

[changeset-bot]

🦋 Changeset detected

Latest commit: 0e883fc

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

This PR includes changesets to release 11 packages

Name	Type
@graphql-codegen/visitor-plugin-common	Major
@graphql-codegen/typescript-operations	Major
@graphql-codegen/client-preset	Major
@graphql-codegen/typescript-document-nodes	Patch
@graphql-codegen/gql-tag-operations	Patch
@graphql-codegen/typescript-resolvers	Patch
@graphql-codegen/typed-document-node	Patch
@graphql-codegen/typescript	Patch
@graphql-codegen/introspection	Patch
@graphql-codegen/graphql-modules-preset	Patch
@graphql-codegen/cli	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