Add JXA-based AppleScript reader for faster read operations

[spiralian]

Summary

Replaces slower osascript AppleScript calls with a JXA (JavaScript for Automation) based reader for all read operations, significantly improving performance and fixing incorrect results.

Problem

The original AppleScript bridge uses the things.py library which queries the Things 3 SQLite database directly. This approach returns incorrect todos — the database contains stale/cached data that doesn't always match what Things 3 actually shows. Items can appear in wrong lists, completed items show as incomplete, and recently moved items appear in their old locations.

Solution

The JXA reader talks to Things 3 directly through its scripting interface (JavaScript for Automation), which always returns the correct, current state of todos — exactly what the user sees in the app.

Changes

• applescript_reader.py (new) — JXA-based reader for all Things 3 read operations
• fast_server.py — refactored to use new reader for list views and searches
• formatters.py — improved with project/area title resolution from IDs
• applescript_bridge.py — cleaned up (write operations remain unchanged)
• test_e2e_applescript_reader.py (new) — e2e tests for the reader
• docs/applescript-migration.md (new) — migration documentation

Benefits

• Correct data — reads from Things 3 directly, not a stale SQLite cache
• Faster — bulk JXA queries instead of multiple sequential osascript calls
• More reliable — no dependency on undocumented database schema