JSON output no longer escapes non-ASCII characters, new --ascii option

[simonw]

refs:

• Doublebyte content is unicode-escaped in JSON output #625

sqlite-utils query/rows/search/tables/views/triggers/indexes/memory now
output JSON with ensure_ascii=False, so unicode text like 日本語 is emitted
directly instead of as \uXXXX escape sequences. This matches how values
were already stored on insert (jsonify_if_needed) and how CSV/TSV output
already behaved.

A new --ascii flag on all of those commands restores the previous escaped
output, for systems that cannot handle UTF-8.

Also applies ensure_ascii=False to the convert --multi --dry-run preview
(matching what would actually be stored) and to plugins listing output.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01JaHan1NhaTRAxJ9LQtSLf9

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.29%. Comparing base (d516e58) to head (823b334).

Files with missing lines	Patch %	Lines
sqlite_utils/cli.py	80.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #777   +/-   ##
=======================================
  Coverage   95.29%   95.29%           
=======================================
  Files           9        9           
  Lines        3652     3652           
=======================================
  Hits         3480     3480           
  Misses        172      172           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.