… addresses

- Replace bare match_phrase street clauses with fuzzyStreetClause() in all 3 layouts
  (AddressesUsingIdsQuery, FallbackQuery, StructuredFallbackQuery)
- fuzzyStreetClause uses multiple strategies: exact phrase, peliasStreet analyzer,
  decompounded variant, concatenated variant, prefix-stripped variant, fuzzy match
- Add createPostcodeAndStreetShould fallback branch in AddressesUsingIdsQuery
  (low-boost PLZ+street without house number for interpolation support)
- Add postcode boost in address should clause
- Add boost_postcode view and export it from index.js

feat: fuzzy street matching, decompounding, postcode boost for German…

Markgrafstr. (query) expands to Markgrafstraße but is indexed as
Markgrafenstraße — a 2-edit difference (insert 'e' and 'n').
Fuzziness 1 missed these matches; fuzziness 2 with prefix_length 5
fixes them without overly broadening unrelated results.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Adds fuzziness:2 prefix_length:8 alongside existing fuzziness:1 to
bridge the German -en- linking element dropped in abbreviations:
"Markgrafstr." → "markgrafstr" is 2 edits from "markgrafenstr".
prefix_length:8 ensures only long-prefix matches (blocks false positives
like "angerstr" vs "angelest" which diverge at position 6).
fuzziness:1 is retained for ö↔oe transliteration (1-edit, no prefix needed).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

PLZ+street-without-housenumber clause surfaced wrong-number PLZ-matching
addresses into top-3, which PLZ-first pick_best then selected over
correct-number interpolated/plz_mismatch results.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The clause surfaces PLZ-matching neighbouring addresses so the interpolation
service can estimate position when the exact housenumber is absent from the
index (e.g. Lorcher Str. 7 in 73547 Lorch). Without it, interpolation
finds no candidates and falls back to a wrong-city result (194km off).

The earlier 50 pick_best regressions were fixed in the benchmark by making
pick_best require PLZ+housenumber match before preferring a PLZ-matching
result — wrong-number PLZ matches no longer override the correct ES-ranked
features[0].

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>