Improve remaining locality GeoNames ID coverage after v0.1.5

[mustafazeydani]

v0.1.5 intentionally leaves locality-level GeoNames ID coverage partial.

Current release coverage:

• Localities: 7,605
• Localities with GeoNames IDs: 4,274
• Localities still missing GeoNames IDs: 3,331
• GeoNames locality ID coverage: 56.2%

Progress tracked so far:

• v0.1.2 added 281 widened-radius one-to-one GeoNames locality matches using exact normalized names and same-governorate checks.
• v0.1.3 added 225 Arabic article-insensitive one-to-one GeoNames locality matches within 2 km.
• v0.1.4 added dated record-level sourceReferences; locality GeoNames coverage remained unchanged.
• v0.1.5 cleaned alias language tags; locality GeoNames coverage remained unchanged.
• The reusable matcher supports dry-run/apply modes and selected Arabic article-insensitive variants.

Current concentration of missing GeoNames IDs by governorate:

• Aleppo: 919
• Al-Hasakah: 876
• Raqqa: 393
• Idlib: 291
• Hama: 223
• Homs: 158
• Latakia: 129
• Tartus: 109
• Deir-ez-Zor: 96
• Daraa: 44
• Rif Dimashq: 42
• Quneitra: 30
• As-Suwayda: 21
• Damascus: 0

Notes:

• Do not infer IDs from name similarity alone.
• Keep every accepted ID source-backed and documented through an import manifest.
• Review remaining candidates in focused governorate batches, starting with Aleppo and Al-Hasakah.
• If a locality has no safe GeoNames match, leave it unresolved until a stronger approved source exists.

Related releases:

• https://github.com/Open-Syria/data-geography/releases/tag/v0.1.5
• https://github.com/Open-Syria/data-geography/releases/tag/v0.1.4
• https://github.com/Open-Syria/data-geography/releases/tag/v0.1.3
• https://github.com/Open-Syria/data-geography/releases/tag/v0.1.2
• https://github.com/Open-Syria/data-geography/releases/tag/v0.1.1

[mustafazeydani]

Reviewed after publishing v0.1.5. This is still valid and should stay open: current locality GeoNames coverage remains 4,274 / 7,605 records (56.2%), with 3,331 localities still missing GeoNames IDs.

I refreshed the issue title/body from v0.1.3 to v0.1.5, noted that v0.1.4 and v0.1.5 did not change locality GeoNames coverage, and added the enhancement label.