fix(NodeNext): add package entrypoints

[ceddybi]

Summary

• Add package exports for the root module, domain subpaths, existing dist deep imports, and register helpers.
• Add typesVersions mappings so subpath type resolution still works for consumers that do not read export-condition types.
• Update the NodeNext consumer fixture to import through published package entrypoints instead of relative dist paths.

Tests run

• yarn test:types:nodenext
• yarn lint
• git diff --check
• ESM/CJS package entrypoint smoke checks
• npm pack --dry-run

Risks / follow-ups

• This keeps the package on the current CommonJS build output; it does not introduce a dual ESM build.
• Strict NodeNext default-import ergonomics remain a separate CommonJS interop concern; this PR focuses on named exports and subpath entrypoints.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1794af08e9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve dist directory deep imports

When consumers still import a directory-style dist subpath such as require('@stoqey/ibkr/dist/account'), this wildcard substitutes account into ./dist/*.js, so Node now resolves /dist/account.js and throws MODULE_NOT_FOUND instead of falling through to /dist/account/index.js; adding an exports map disables the previous package subpath directory resolution. Since the change explicitly aims to keep existing dist deep imports working, add explicit ./dist/account, ./dist/connection, etc. index entries (and ./dist if needed) rather than relying only on the file wildcard.

Useful? React with 👍 / 👎.