fix: remove engines.node from published package

The browser-only published library declared engines.node ">=24",
which hard-fails consumer installs on Node 20/22 LTS under
engine-strict (#165). The published dist only uses browser APIs
(window, navigator, WebGL, fetch) and needs no Node runtime.

The build/publish Node version is already pinned to 24 independently
of this field via .nvmrc and the '24' node-version in both CI
workflows, so dropping engines does not affect building or
publishing. This restores the v6.0.0 behavior (no engines field).

Fixes #165

Author: puckey

README.md

@@ -145,7 +145,6 @@ getGPUTier({
 
 ## Requirements
 
-- Node.js 24+
 - ESM only (CommonJS is not supported)
 
 ## Support

package.json

@@ -2,9 +2,6 @@
   "name": "@pmndrs/detect-gpu",
   "version": "6.0.9",
   "packageManager": "pnpm@10.13.1",
-  "engines": {
-    "node": ">=24"
-  },
   "description": "Classify GPU's based on their benchmark score in order to provide an adaptive experience.",
   "author": "Tim van Scherpenzeel",
   "license": "MIT",