Update package json exports to include type definitions

[patrickjm]

Related to #2323

Description

Typescript 5.0 is in beta, and it adds a couple new compiler options.

If you want to use the new moduleResolution mode "bundler" or compiler option "resolvePackageJsonExports", Typescript will ignore the top-level "types" field in your package.json and only look for types inside package.json "exports".

See: microsoft/TypeScript#52363

That means, types need to be directly pointed at in package.json exports.

Partially addresses #2323

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

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 and linter rules pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[changeset-bot]

🦋 Changeset detected

Latest commit: 3a341c7

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

This PR includes changesets to release 1 package

Name	Type
graphql-modules	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

[dotansimha]

Thanks @patrickjm !