fix(geocoding): drop unused Pelias services, raise Bun idleTimeout

Two production follow-ups surfaced after the deploy:

1. Pelias API was emitting continuous `ENOTFOUND placeholder`, `pip`,
   `interpolation` errors because we declared those services in
   pelias.json but never actually run them (we don't need WOF
   admin lookup or street interpolation for the DACH use case).
   Removed the stale entries — Pelias degrades cleanly to
   libpostal-only parsing, which is what we want.

2. Bun.serve's default idleTimeout is 10s, which is too tight for
   cold Pelias queries hitting Elasticsearch. Raise to 60s so
   first-query-after-idle doesn't get cut off.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

services/mana-geocoding/pelias/pelias.json

@@ -12,15 +12,6 @@
 		"services": {
 			"libpostal": {
 				"url": "http://libpostal:4400"
-			},
-			"placeholder": {
-				"url": "http://placeholder:4100"
-			},
-			"pip": {
-				"url": "http://pip:4200"
-			},
-			"interpolation": {
-				"url": "http://interpolation:4300"
 			}
 		},
 		"defaultParameters": {}

services/mana-geocoding/src/index.ts

@@ -16,5 +16,9 @@ console.log(`Pelias API: ${config.pelias.apiUrl}`);
 
 export default {
 	port: config.port,
+	// Bun's default idleTimeout is 10s — too tight for Pelias cold queries
+	// that need to hit Elasticsearch and libpostal. 60s is generous enough
+	// for the worst-case while still cutting off stuck connections.
+	idleTimeout: 60,
 	fetch: createApp(config).fetch,
 };