fix: correct package entrypoints for 1.6.8 dist output

[yyxi]

This patch fixes broken package entrypoints in v1.6.8.

Root cause:

• Introduced in commit 73a7184 (chore: bump up deps chore: bump up deps #871).
• tsdown was upgraded from ^0.15.10 to ^0.20.3.
• Build output changed from index.js/index.d.ts to index.mjs/index.d.mts, but package.json still pointed to index.js/index.d.ts.

Changes:

• module -> ./dist/index.mjs
• types -> ./dist/index.d.mts
• exports["."].import -> ./dist/index.mjs
• exports["."].types.import -> ./dist/index.d.mts
• exports["."].types.require -> ./dist/index.d.cts

Verification:

• pnpm build
• pnpm typecheck
• pnpm test
• npm pack confirms all referenced files are present

[yyxi]

@veritem Thanks for the release work here. This looks like a patch-level regression with downstream impact: v1.6.8 publishes dist/index.mjs and dist/index.d.mts, while package entrypoints still reference dist/index.js and dist/index.d.ts. That mismatch breaks module resolution in consumers (for example ESLint config loading).

This PR only updates package.json entrypoints to match the published dist output and keeps CommonJS and type paths aligned.

[veritem]

thanks