Fixes to run on current Node.js versions and handle crash reports from current clients

[Jimbly]

This is a collection of fixes I needed to make as I updated my servers from Node 16 to Node 22, and added an Electron-based client submitting crash reports (uses crashpad, not breakpad, on the front end, which shouldn't matter, but apparently hit some bug in busboy).

• Add package-lock.json for more easily installing a currently known-good set of dependencies
• Replace minidump with @jimbly/minidump
  • Includes update to minidump@0.22 to support Node 22.x+
  • Includes not-yet-merged PRs to fix:
    • (Linux binaries only) Uses latest breakpad version to support parsing dumps sent from Windows 11 22H2 clients minidump/#94
    • Fixes failing to install outside of git repositories or if yarn is not installed minidump/#95
    • Fixes callback being called multiple times upon error minidump/#97
    • Allow installation on Windows again
    • Includes pre-built (albeit old) Win32 binaries for Windows since the current version of Breakpad no longer compiles for Windows
• Allow viewing crash dump information even if minidump_stackwalk fails to execute
• Update to latest connect-busboy
  • Fixes two 'finish' events emitted when handling uploads from Electron/crashpad, causing "headers already sent" error (which was showing up as "[Object object]" in the console)
• Fix caught Errors turning into [Object object] on the console
• Add missing grunt-shell dependency
• Upgrade to sqlite3@5 to support Node 16.x+

As of this update, I'm running the latest version here in production on a Node v22.12.0 server, with a sqlite database backend, and successfully receiving crash reports from older breakpad and Electron/crashpad clients (and, very importantly, actually getting useful callstacks from those old clients when running on Windows 11 which apparently broke some months ago due to an dbghelp.dll update in Windows, although the dumps were still valid and debuggable, of course).