Location search now handles typos and punctuation

When you look up a location, you no longer have to type it exactly the way our catalog stores it. Common variations — missing punctuation, dropped apostrophes, and plain typos — now resolve to the right city instead of coming back empty.

Before, small differences would return 0 results even when the city clearly existed. Now they just work:

• St Petersburg (no period) → resolves to St. Petersburg
• St. Petersburg, FL → ranks St. Petersburg, Florida first, ahead of the more populous Saint Petersburg in Russia
• coeur dalene (missing apostrophe) → resolves to the right city in Idaho
• los angelos, manchster, san fransico (typos) → resolve to Los Angeles, Manchester, and San Francisco

Adding a state also helps us pick the right match: when two cities share a name, the qualifier you type guides which one comes first.

This applies everywhere location lookup happens — autocomplete in the app, the /v0/catalog/locations API endpoint, and the MCP server. Exact and partial inputs are unchanged; we only step in to catch the variants that used to fall through.