sqlite: add batched async Database API

[BurningEnlightenment]

This PR adds the asynchronous complements Database and Statement to the node:sqlite module.

Given that a single sqlite db connection cannot scale beyond a single CPU core, (unlike the old sqlite3) this implementation avoids unordered dispatches to the thread pool by maintaining a strict FIFO operation queue. This allows usage of multiple db connections in parallel without relying on the internal db connection mutex (=> SQLITE_THREADSAFE=2 is sufficient). Furthermore I've favored throughput over latency, e.g. it collects asynchronous operations on a db connection and dispatches them in batches to the thread pool. This helps to amortize the inherent synchronization overhead over multiple operations and it also improves cache locality.

The implementation effort has reached a maturity level where the overall approach should only require relatively small incremental changes to reach the outlined API scope. Briefly the following things work:

• Opening a db connection and (asynchronously) preparing statements.
• Disposal of db connection and statement instances.¹
• Database.prototype.exec() without a prepared statement.
• Statement.prototype.get() with binding parameters (though currently not as fancy as the sync variant).
• Implicit microtask-based batching of all previously mentioned operations (inspired by kysely).

Things which still need work:

• Function parameter validation should not throw but return rejected promises.
• From a brief look it seems that direct usage of v8::Promise looses the async context/callstack. I need some guidance on how to fix that.
• An explicit batching API, either callback- or Symbol.dispose/using-based (different PR?)
• Explore an API to move a db connection from Database to DatabaseSync and vice versa (different PR?)
• Proper API documentation
• Probably a few extensions to the test suite here and there.
• The memory allocation strategy should be tweaked to use std::pmr::monotonic_buffer_resource in a few places.
• Obviously implementing the remaining APIs outlined below.

Fixes #54307
Previous attempt #59109 (I've only taken the test suites from there).

API synopsis

interface DatabaseOpenOptions {
    // IN PROGRESS (currently same as sync, though partially not respected)
}
interface DatabaseCtor {
    new(path: string, options?: DatabaseOpenOptions): Database;
}
interface Database {
    open(): void;
    isOpen: boolean;
    close(): Promise<void>;
    [Symbol.asyncDispose](): Promise<void>;

    location(dbName?: string): Promise<string|null>; // TODO
    loadExtension(path: string): Promise<void>; // TODO
    enableLoadExtension(allow: boolean): Promise<void>; // TODO
    enableDefensive(active: boolean): Promise<void>; // TODO

    inTransaction(): Promise<boolean>; // TODO

    exec(sql: string): Promise<void>;
    // IN PROGRESS (statement options are ignored)
    prepare(sql: string, options?: StatementOptions): Promise<Statement>;
}

type Literal = null | number | bigint | string | ArrayBufferView;
type BindParams = Record<string, Literal> | Array<Literal>;
type RowResult = Record<string, Literal> | Array<Literal>;
interface Statement {
    [Symbol.dispose](): void;

    get(params?: BindParams): Promise<RowResult | undefined>;
    all(params?: BindParams): Promise<RowResult[]>; // TODO
    run(params?: BindParams): Promise<{ changes: number, lastInsertRowid: number }>; // TODO
}

---

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Footnotes

1. I've followed the spirit of DEP0137; should probably be reconciled with the sync API at some point. ↩

[nodejs-github-bot]

Review requested:

• @nodejs/gyp
• @nodejs/security-wg
• @nodejs/sqlite

[BurningEnlightenment]

@geeksilva97 given that you spearheaded the previous attempt, what are your thoughts regarding this approach?