Fix NPM packages exports and metadata

[romelperez]

Fixes #698

• Add NPM packages files setting with only ./build package folder.
• Add NPM packages metadata.

To help everyone out, please make sure your PR does the following:

• Update the first line to point to the ticket that this PR fixes
• Add a message that clearly describes the fix
• If applicable, add a test that would fail without this fix
• Make sure the unit and integration tests pass locally with pnpm run tests and cd integration && pnpm run tests
• Includes a changeset if your fix affects the user with pnpm changeset

[changeset-bot]

⚠️ No Changeset found

Latest commit: 75d4bba

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

[vercel]

@romelperez is attempting to deploy a commit to the HoudiniGraphQL Team on Vercel.

A member of the Team first needs to authorize it.

[romelperez]

The final build folder in the NPM package release has 26MB. But anyway, it will prevent to ship unwanted code to NPM.