test: E2E sqlite3 CLI seeding has no busy timeout (flaky 'database is locked') #606

test-region-scope-approval-e2e.js failed on master (CI run 40205480480, E2E shard 3) with:

Error: stepping, database is locked (5)
test-region-scope-approval-e2e.js: FAIL — Error: Command failed: sqlite3 … INSERT INTO observer_neighbors(…)

The test seeds rows with the sqlite3 CLI (execFileSync('sqlite3', [env.db, statement]), line 137) while the ingestor may hold a write lock. The CLI has no busy timeout, so it fails at once instead of waiting.

Fix: give the CLI a busy timeout (for example ['-cmd', '.timeout 5000', env.db, statement]) and check other E2E/test helpers that shell out to sqlite3 against a live DB for the same pattern. Add a regression check (e.g. a static test that every sqlite3 CLI call in E2E helpers sets a timeout).