chore(deps): upgrade to Next.js 16, Vitest 4, and Node.js 24

[MickLesk]

✍️ Description

BREAKING CHANGES:

• Upgrade Next.js from 15.1.6 to 16.0.4
• Use Webpack instead of Turbopack for compatibility with server-side modules
• Upgrade Node.js requirement to >=24.0.0

FEATURES:

• Upgrade Vitest to 4.0.13 with improved testing capabilities
• Update all vitest-related packages (@vitest/ui, @vitest/coverage-v8)
• Upgrade react-syntax-highlighter to 16.1.0
• Update node-cron to 4.2.1
• Update lucide-react to 0.554.0

SECURITY:

• Resolve glob command injection vulnerability (CVE) via v10.5.0
• Fix all npm audit vulnerabilities (0 vulnerabilities found)
• Update prisma/client to 6.19.0
• Update all dependencies to latest secure versions

FIXES:

• Configure next.config.js for webpack with proper server-side module handling
• Update tsconfig.json for Next.js 16 compatibility (jsx: react-jsx)
• Add engines field to require Node.js >=24.0.0
• Remove deprecated webpack config in favor of Next.js 16 compatibility

🔗 Related PR / Issue

Link: #307 #325 #330 #332 #334

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

Screenshot for frontend Change

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.

[MickLesk]

@michelroegl-brunner need to test in an live Environment or as upgrade, i only had to test with my Linux Mint DEV-PC (localhost)

[michelroegl-brunner]

I test it tommorow or on wendsday. I merge it for now, i wont do a release for now.