fix(places): a locality collision must not break the sitemap

Sitemap regeneration failed on staging. 'richmond' in the curated locality
list collides with the GIAS town Richmond in North Yorkshire (37 schools), the
registry raised, and the admin endpoint 500d — taking down sitemap generation
for all 25,000 school pages over one bad row of curated data.

The guard now skips the colliding locality and logs an error. Skipping still
achieves what the guard was for — a locality never silently shadows a town —
without letting curated data break the site. That matters beyond this bug:
GIAS town names change with no code change here, so a raise could fire
spontaneously in production later.

Also removes four localities that were London boroughs rather than districts.
Hackney, Islington, Greenwich and Ealing are local authorities with 104, 72,
108 and 115 schools and already have authority pages; a locality defined by
two or three outcodes would have been a partial near-duplicate of one — the
thin-content failure the two-namespace design exists to avoid. A test now
guards the whole borough list.

Validated against the live corpus: 15 localities, no town collisions, no
authority duplicates, all 15 clear the threshold.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015mWQnpye9F299NVRCCSRvj

pipeline/transform/seeds/locality_outcodes.csv

@@ -5,16 +5,11 @@ clapham,Clapham,SW4,London
 shoreditch,Shoreditch,EC2A|E1,London
 peckham,Peckham,SE15,London
 brixton,Brixton,SW2|SW9,London
-hackney,Hackney,E5|E8|E9,London
-islington,Islington,N1|N5|N7,London
 camden-town,Camden Town,NW1,London
-greenwich,Greenwich,SE10,London
 wimbledon,Wimbledon,SW19,London
 putney,Putney,SW15,London
 fulham,Fulham,SW6,London
 chiswick,Chiswick,W4,London
-ealing,Ealing,W5|W13,London
-richmond,Richmond,TW9|TW10,London
 stratford,Stratford,E15,London
 walthamstow,Walthamstow,E17,London
 tooting,Tooting,SW17,London