Refactor server to run in all (Node.js compatible) runtimes and meta frameworks (#710)

Refactor the request handlers and hooks to be based on `Request` (from the fetch API) instead of `http.IncomingMessage`/`http.ServerResponse` (which are Node.js specific) as we can turn the Node.js ones into `Request`/`Response` but not the other way around. That means we can have a `handle(req, res)` method for Node.js servers and a `handleWeb(req)` for other runtimes and meta-frameworks (such as Next.js React Router, SvelteKit, etc) which both use the same core logic.

Author: Murderlon

.changeset/polite-bikes-train.md

@@ -0,0 +1,13 @@
+---
+"@tus/server": major
+---
+
+- Introduce `handleWeb(req: Request)` to integrate into meta frameworks
+  (such as Next.js, Nuxt, React Router, SvelteKit, etc) and other Node.js compatible runtime environments.
+- All events and hooks now emit `Request`/`Response` instead of `http.IncomingMessage`/`http.ServerResponse`.
+- The function version of the options `maxSize`, `generateUrl`, `getFileIdFromRequest`, `namingFunction`, `locker`
+  also now use `Request`/`Response`.
+- Your `onUploadCreate` and `onUploadFinish` hooks no longer need to return the response object.
+  - If you want to change the metadata in `onUploadCreate` you can return `Promise<{ metadata: Record<string, string> }>`.
+    This will will internally merge the existing metadata with the new metadata.
+  - `onUploadFinish` can return `Promise<{ status_code?: number headers?: Record<string, string | number> body?: string }>`

biome.json

@@ -4,14 +4,17 @@
     "enabled": true
   },
   "files": {
-    "ignore": ["./**/dist/**/*"]
+    "ignore": [".git", "node_modules", "./**/dist/**/*"]
   },
   "linter": {
     "enabled": true,
     "rules": {
       "recommended": true,
       "style": {
         "noParameterAssign": "off"
+      },
+      "performance": {
+        "noDelete": "off"
       }
     }
   },