fix: avoid leaking @types/node into client code

[aleclarson]

Overview

The defineWxtPlugin function is referenced by the generated .wxt/types/imports.d.ts module, which is used by client code. Therefore, we need to avoid importing from wxt/src/types.ts, as it depends on Node.js-specific packages (like vite). This inadvertently introduces Node.js globals into the extension's client environment, which is undesirable (e.g. it breaks the return type of setTimeout).

Edit 1

Updated other "offending" imports. Split out the option-related types (into option-types.ts) and the client-related types (into client-types.ts).

Manual Testing

Without this change, you should see setTimeout return a NodeJS.Timeout object.

After this change, setTimeout will return a number as expected.

Related Issue

#1459

[netlify]

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	54b8603
🔍 Latest deploy log	https://app.netlify.com/sites/creative-fairy-df92c4/deploys/67dedb998bb9b00008912f85
😎 Deploy Preview	https://deploy-preview-1531--creative-fairy-df92c4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[aleclarson]

I can retarget this to #1085 if you prefer. LMK!