Use Node.js native sqlite instead of better-sqlite3

[i-am-the-slime]

Replace better-sqlite3 with Node.js native node:sqlite module.

• Requires Node.js >= 22.5.0 (see release schedule)
• Named parameter syntax changed slightly (@param with object argument)
• Suppresses ExperimentalWarning in CLI and tests

[wclr]

Maybe it is better to move to nodejs build-in sql support https://nodejs.org/api/sqlite.html (available from Node 22)

Spago next is a new tool and still not widely used so I don't think that there need to worry about old node version and ignore node platform development.

[i-am-the-slime]

@wclr sure, let's get some buy-in first from the maintainers and then we can also go that route.

Main motivation is to avoid having to rebuild spago for different node versions.

[f-f]

Removing all the warnings is a terrible idea for a set of reasons 😄

Let's just exclude the warnings for experimental modules: --no-warnings=ExperimentalWarning

[f-f]

Node will fail with a horrible error if it doesn't find the module, so I think we should catch it at the startup and error out then.

Implementation sketch:

import Data.Int as Int
import Data.String as String
import Effect.Console as Console
import Node.Process as Process

-- first thing inside main:
main = do
  -- Check that we're running on Node.js >= 22.5.0 (required for node:sqlite)
  let
    -- version is like "v22.5.0" or "22.5.0"
    versionStr = String.stripPrefix (String.Pattern "v") Process.version
      # fromMaybe Process.version
    parts = String.split (String.Pattern ".") versionStr

  case Array.take 2 parts >>= traverse Int.fromString of
    Just [major, minor]
      | major > 22 -> pure unit
      | major == 22 && minor >= 5 -> pure unit
      | otherwise -> do
        Console.error $ "Error: spago requires Node.js v22.5.0 or later (found " <> Process.version <> ")"
        Process.exit' 1
    _ -> do
      -- couldn't parse, issue a warning and let it crash later
      ..

together with this we should also add the engines field to the package.json. Node won't enforce it on install, but will complain about it:

 {                                                                                                      
    "engines": {                                                                                         
      "node": ">=22.5.0"                                                                                 
    }                                                                                                    
  }  

[f-f]

why are we ignoring the error here?

[f-f]

we use positional arguments in a few places, we should use them everywhere, e.g.:

Suggested change

	.prepare("SELECT * FROM package_sets WHERE compiler = ? ORDER BY date DESC LIMIT 1")
	.get(compiler);
	.prepare("SELECT * FROM package_sets WHERE compiler = @compiler ORDER BY date DESC LIMIT 1")
	.get({ compiler });

[f-f]

The existing code is in Effect, and this database code is sync as well, why turn everything into Promises?