fix: remove why-is-node-running from prod

Still sticking around for development - it works well, but I suspect
it's causing some nasty long-term memory leaks, since all my projects
using it are reaching 1.5 GB memory after ~2 months.

package.json

@@ -1,12 +1,12 @@
 {
   "name": "krist",
-  "version": "3.5.2",
+  "version": "3.5.3",
   "description": "The new Krist node written in TypeScript.",
   "type": "module",
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "start": "node dist/src/index.js",
-    "dev": "tsx src/index.ts",
+    "dev": "tsx --import why-is-node-running/include.js src/index.ts",
     "docs": "apidoc -v -t apidoc-template -i src -o static/docs",
     "test": "cross-env TS_NODE_PROJECT='./tsconfig.test.json' NODE_ENV=test mocha 'test/**/*.test.ts'",
     "test:coverage": "nyc pnpm run test",

src/index.ts

@@ -22,7 +22,6 @@
 import "dotenv/config";
 
 import chalkT from "chalk-template";
-import whyIsNodeRunning from "why-is-node-running";
 import packageJson from "../package.json" with { type: "json" };
 import { initDatabase, shutdownDb } from "./database/index.js";
 import { initRedis, shutdownRedis } from "./database/redis.js";
@@ -60,11 +59,6 @@ function shutdown() {
     shutdownAuthLogCleanup();
     shutdownWebSocketIpc();
   })().catch(console.error);
-
-  setTimeout(() => {
-    console.log("Still shutting down?");
-    whyIsNodeRunning();
-  }, 8000).unref();
 }
 
 process.on("SIGINT", shutdown);