fix: sync _TOWN_ANCHORS_SEED with the production town_anchors table

_TOWN_ANCHORS_SEED covered only 29 hand-picked towns, while the live
CT108 town_anchors table (GUI-curated since) has grown to 186. Any
fresh deploy (fresh volume, or the pre-v19 sqlite path) would seed
only the original 29 and silently lose anchor-resolution coverage for
the other 157 real, already-in-production towns.

Regenerated the dict from a live dump of CT108's town_anchors
(name, lat, lon, state; all 186 rows confirmed enabled=1), alphabetized,
same dict-of-dicts shape and column-aligned brace formatting as before
(alignment column widened to fit the longest name, "mountain home
afb"). seed_town_anchors() is unchanged and still INSERT OR IGNORE, so
it stays idempotent against the existing production rows.

Expanding the seed changes which town resolves as "nearest" for a few
existing test fixtures whose incident/work-zone coordinates are
genuinely closer to a newly-added real town (e.g. Oakley, Wilder) than
to the old 29-town subset's nearest match -- those goldens and
assertions are updated to the new (correct) nearest-town result.
test_api_post_add_town's probe town is renamed from the now-real
"Bellevue" to a fictitious "Testopolis" to avoid a duplicate-name 400.

work/tests/test_fire_refactor.py

@@ -217,7 +217,10 @@ class TestFormatterGolden:
         # Golden literal (captured from the live fire_format all-clear branch;
         # this is the SAME format string handle_wfigs used to build inline
         # before its removal -- see notifications/formatters/fire.py::_render_allclear).
-        assert new_wire == "✅ Cache Peak Fire — contained & closed\n1,847 ac | 23% contained | 24 mi S of Burley"
+        # "oakley" is nearer to 42.197,-113.710 than "burley" and is now in
+        # the town_anchors seed after the seed-list sync (Fix 2), so it wins
+        # the anchor resolution instead of the previously-nearest seeded town.
+        assert new_wire == "✅ Cache Peak Fire — contained & closed\n1,847 ac | 23% contained | 9 mi E of Oakley"
 
 
 # ─────────────────────────────────────────────────────────────────────────────