feat(plugin/typescript-resolvers): Add allowSemanticNonNull option

[Quramy]

Description

Related #10151 .

Added a new option for plugin/typescript-resolvers, allowSemanticNonNull.

Several GraphQL frameworks work with @semanticNonNull schema directive:

• https://relay.dev/docs/guides/semantic-nullability/#proposed-solution
• https://www.apollographql.com/docs/kotlin/advanced/nullability/#semanticnonnull

If allowSemanticNonNull option is set to true, field resolver annotated by @semanticNonNull gets prohibited to return nullish.

For example:

type User {
  name: String @semanticNonNull
}

The above schema and allowSemanticNonNull: true generates the following resolver type:

export type UserResolvers<ContextType = BaseContext, ParentType extends ResolversParentTypes['User'] = ResolversParentTypes['User']> = {
  name?: Resolver<ResolversTypes['String'], ParentType, ContextType>;
  __isTypeOf?: IsTypeOfResolverFn<ParentType, ContextType>;
};

import type { UserResolvers } from "./_gql_gen_generated_/"

export const User = {
  name:  () => {
    // @ts-expect-error
    return null;
  }
} satisfies UserResolvers

Type of change

• New feature (non-breaking change which adds functionality)

Screenshots/Sandbox (if appropriate/relevant):

Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit Testing

Test Environment:

• OS: macos Sonoma
• NodeJS: v20.14.0

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Further comments

[changeset-bot]

⚠️ No Changeset found

Latest commit: 199b538

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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