Multilingual card search (integrates #1 by @w-dan)

[madeofpendletonwool]

Integrates @w-dan's multilingual card search from #1, rebased onto current main with the merge conflict resolved and a few integration fixes.

All feature credit goes to @w-dan (Dani) — see #1 for the original work and write-up. Closes #1.

What the feature does

Cards can now be found by their foreign names (e.g. "Gegenzauber" or "対抗呪文" → Counterspell). The root cause was the import script reading fd.faceName, which MTGJSON only populates for multi-face cards, leaving foreign_name null for single-face cards; it now reads fd.name.

Conflict resolution (src/services/cardService.js)

searchCards() on main had since gained a typeFilter parameter (used by the price-watch card type filter via src/routes/cards.js). The PR was written against the older two-arg signature and dropped it, so merging as-is would have silently broken the card type filter.

• Combined both: foreign-name matching and typeFilter.
• Parenthesised the name-match OR group so the type filter ANDs against the whole group rather than only the last OR branch.
• Dropped a redundant LIMIT 1 inside EXISTS().

Integration fixes

• Index moved to its own migration. idx_foreign_name was added inside migration 010, which is already applied on existing installs — the runner would never re-run it, so only fresh databases would get the index. Now in 020-add-foreign-name-index.js using CREATE INDEX IF NOT EXISTS.
• Removed 017-add-card-search-fts.js. It collided with the existing 017-add-price-watches.js, and the FTS5 table it created was never populated or queried. The original PR's own commit 5cac99c "Removed FTS search (found to be unnecessary)" had already dropped FTS usage but left the migration behind.

Notes for testing

The import-script change only takes effect after a card database re-import, so this needs a Docker run with a re-import to see multilingual results.

Two things worth knowing (both pre-existing, not regressions):

• Search returns one row per printing, so a card with many printings can crowd out other matches under LIMIT.
• Foreign matching uses EXISTS(... LIKE '%query%') joined on card_name = c.name, which can't use the new index; may be slow on a large card_foreign_data table.