fix(sqlite): Statement.run() and Database.exec() now return Changes object

[David Anderson (akapug)]

Summary

Updates Statement.run() and Database.exec() to return a Changes object instead of undefined, matching the Bun SQLite API.

Problem

Per the TypeScript types and Bun compatibility, run() and exec() should return a Changes object:

interface Changes {
  changes: number;        // rows affected
  lastInsertRowid: number | bigint;
}

Previously:

• Statement.run() returned Unit (undefined in JS)
• Database.exec() returned Undefined.instance

Solution

1. New SQLiteChanges interface - Defines the contract matching Bun's Changes
2. SQLiteChangesImpl - Internal implementation as a ProxyObject for JS interop
3. Updated exec() - Now captures update count and last insert rowid from JDBC
4. Updated run() - Returns the result from exec()

Changes

File	Change
SQLiteChanges.kt	New interface
SQLiteStatement.kt	run() returns SQLiteChanges
SQLiteDatabase.kt	exec() returns SQLiteChanges
SqliteModule.kt	Implementation

Usage

const db = new Database(":memory:");
db.run("CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)");

const result = db.run("INSERT INTO users (name) VALUES (?)", ["Alice"]);
console.log(result.changes);        // 1
console.log(result.lastInsertRowid); // 1

Fixes

Fixes #1791