test: an earlier spec leaves an open transaction on a pooled BoxLang + SQLite connection #4508

What happens. In the full core suite on BoxLang + SQLite, a spec can drop a table and still see it through a later query on another pooled connection:

• DROP TABLE wheels_jobs succeeds;
• a catalog check (sqlite_master) right after it reports the table gone;
• yet the next SELECT ... FROM wheels_jobs (from framework code, on another pooled connection) still finds the table.

It shows up only in the full suite. Running directory=wheels.tests.specs.jobs alone passed four times in a row.

Likely cause. An earlier spec leaves a pooled connection inside an uncommitted transaction (autocommit off). The SQLite test datasource uses the default rollback journal, not WAL. So a later DROP that lands on that connection runs inside the open transaction:

• that connection sees the table gone;
• other connections still see it until the transaction ends.

This is a suite-isolation leak, not a product bug. It makes "drop, then expect missing" specs order-dependent on BoxLang + SQLite.

Where it was seen.

• In JobSchemaSpec (feat(cli): wheels jobs install and jobsAutoCreateTables #4499), in the full BoxLang + SQLite suite, locally and on one full-matrix leg; PR CI passed at the same head.
• The affected spec now no longer drops anything: it simulates the failure with a datasource that doesn't exist.
• The schema specs' drop helpers now confirm the drop through the catalog and fail with the DROP's error instead of swallowing it.
• Other drop-then-expect-missing specs (for example JobSchemaSpec's "creates nothing with jobsAutoCreateTables = false") can still hit it, depending on order.

To do.

• Bisect which earlier spec (or spec directory) leaves the open transaction on BoxLang + SQLite. Candidates include specs that open transaction action = "begin" themselves, or that leave one open on an error path; the database/ and model/ directories run before jobs/.
• Fix the leak at its source (commit or roll back in that spec's afterEach, or end any open transaction in the test runner between bundles), rather than making each later spec defensive.

Acceptance criteria.

• The leaking spec is identified and fixed.
• A drop-then-expect-missing spec passes in the full BoxLang + SQLite suite regardless of order.