fix(build): ensure correct typing for node esm

[xiaoxiangmoe]

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

⚠️ Slowing down new functions

Warning: Slowing down new functions

As the VueUse audience continues to grow, we have been inundated with an overwhelming number of feature requests and pull requests. As a result, maintaining the project has become increasingly challenging and has stretched our capacity to its limits. As such, in the near future, we may need to slow down our acceptance of new features and prioritize the stability and quality of existing functions. Please note that new features for VueUse may not be accepted at this time. If you have any new ideas, we suggest that you first incorporate them into your own codebase, iterate on them to suit your needs, and assess their generalizability. If you strongly believe that your ideas are beneficial to the community, you may submit a pull request along with your use cases, and we would be happy to review and discuss them. Thank you for your understanding.

---

Description

According to https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html#packagejson-exports-imports-and-self-referencing
the only way to correct provide types for both Node ESM and CJS is to have two separate declaration files, so we need to generate .d.mts and .d.cts upon build.

Additional context

see vuejs/core@d621d4c

---

🤖 Generated by Copilot at 0986352

This pull request improves the type definition support for the vueuse packages and components, especially for the Vue 3 script setup and module script syntax. It fixes or removes the types and exports fields in the package.json files of each package to avoid conflicts or errors with TypeScript and bundlers. It also generates different type definition files (.d.cts and .d.mts) for each syntax and re-exports them from the core package. It updates the build and fix scripts to handle the new type definition files.

🤖 Generated by Copilot at 0986352

• Use .d.cts and .d.mts files for type definitions instead of .d.ts files to support script setup and module script syntax (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
• Re-export type definitions from metadata package in core package to avoid importing .d.ts files (link, link)
• Copy .d.cts and .d.mts files locally in build.ts script (link)
• Format and lint .d.cts and .d.mts files in fix-types.ts script (link)