Add municipality and coordinate search, and a map target selector

Puts the controls that change what the map is looking at over the map itself,
where they act, and gives them something to search.

Search is one field, not two. A string either parses as coordinates or it does
not, and the answer is obvious from the text, so making the user declare up
front which kind of thing they are looking for would be asking them to do the
program's job. Coordinates accept decimal and degrees-minutes-seconds, comma or
space separated, with hemisphere letters — including the Italian O for ovest,
because someone reading an Italian map will type it and silently reading it as
east would put them the wrong side of Greenwich.

The 1180 Piedmont municipalities are bundled rather than geocoded online. The
app is region-scoped, so a list of one region's towns is small enough to ship
(100 KB) and beats a geocoder on every axis that matters: instant, offline, no
API key, no rate limit, and it cannot return a result somewhere the app has no
radar for. Matching folds accents, so "aglie" finds "Agliè", and prefix matches
outrank substring ones — typing "tor" should surface Torino, not the first
alphabetical name that happens to contain those letters.

tool/generate_places.py derives the list from Istat boundary shapefiles
(CC BY 4.0). Two properties of that file cost time and are now written down:
the geometry is UTM 32N rather than degrees, and the DBF is UTF-8 despite one
bilingual Friulian record that makes strict cp1252 fail. A terminal renders
utf-8 and latin-1 output identically, so the encoding cannot be settled by
looking at printed text — it took dumping codepoints. A guard in the generator
and a test against the shipped asset both check for mojibake now, and the guard
caught a real mistake the moment it was written.

The target selector switches between following the device, a saved place, and
the whole region, and the selection doubles as what the app reopens on: "the
place I marked" and "what I see when I open the app" are one idea to the person
using it. Dragging the map while it is following stops the camera chasing them
but leaves that preference alone, because looking somewhere else now is not the
same as changing their mind about next launch.

The position marker and the following are MapLibre's own, driven by
onCameraTrackingDismissed, so there is no second location stream to keep in step
with the map.

A test asserts that all 1180 municipalities fall inside the region bounds, which
is what actually validates the UTM-to-degrees conversion end to end.

Verified on the emulator: the dropdown lists follow, region and both saved
places; "aglie" finds Agliè; "44.3841 7.5426" offers the coordinate jump and
lands on Cuneo at town-reading zoom; selecting follow moves the map to the
device position with the blue dot on it and changes the recentre button to
match.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Nuvolari/docs/roadmap.md

@@ -78,7 +78,7 @@ and a disk layer belongs with the network adapter, where it would save a real re
 
 ---
 
-## M4 — Saved places and device location ✅
+## M4 — Places, search and device location ✅
 
 A named point the user keeps, used to frame the map and — once notifications exist — to
 anchor them. Stored in `SharedPreferences` on the device and nowhere else.
@@ -104,6 +104,22 @@ A unit test also caught an id collision: ids came straight from the microsecond
 so two places saved in the same microsecond shared an id and rename, remove and the
 duplicate check all acted on the wrong one.
 
+**Extended** with search and a target selector, also verified on the emulator:
+
+- One search field takes either a municipality name or coordinates, because a string
+  either parses as coordinates or it does not and the user should not have to declare
+  which they meant. Accent-insensitive: typing "aglie" finds "Agliè". Coordinates accept
+  decimal and degrees-minutes-seconds, comma or space separated, with hemisphere letters
+  including the Italian **O** for west.
+- The 1180 municipalities are bundled from Istat boundaries rather than geocoded online.
+  A test asserts every one of them falls inside the region bounds, which is what
+  validates the UTM-to-degrees conversion end to end.
+- A dropdown over the map switches between following the device, a saved place, and the
+  whole region; the selection is also what the app reopens on. Dragging the map while it
+  is following stops the camera chasing but leaves that preference alone.
+- The blue position marker and the following are MapLibre's own, so there is no custom
+  location stream to keep in step with the map.
+
 ## M5 — Backend worker ⛔
 
 The critical path. Until this exists, `DpcRadarSource` has nothing to read and the app