sqlite: db.prepare(sql).set* chain

[mike-git374]

This implements Proposal 1 of issue #61235

[nodejs-github-bot]

Review requested:

• @nodejs/sqlite

[himself65]

Could you please update the test case?

[mike-git374]

I updated all tests with statement.set* functions

[Renegade334]

I'm -0.5 on this, as repeated calls across the JS-C++ boundary to set statement options is a very much less efficient paradigm than the alternative proposal, which was to allow options to be passed to prepare(). Passing a consolidated options object to set statement options also matches the pattern already in use in the database constructor.

[mike-git374]

I updated the issue to address this and now recommend db.prepare(sql[, options]) as an alternative to or in addition to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.53%. Comparing base (95852d7) to head (302305c).
⚠️ Report is 41 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #61263 +/- ##
==========================================
- Coverage 88.54% 88.53% -0.02% 
==========================================
Files 704 704 Lines 208753 208757 +4 Branches 40280 40288 +8 ==========================================
- Hits 184847 184820 -27 - Misses 15907 15952 +45 + Partials 7999 7985 -14 

Files with missing lines	Coverage Δ
src/node_sqlite.cc	80.20% <100.00%> (+0.03%)	⬆️

... and 29 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mike-git374]

Closing in favor of Proposal 2