Enable KML output for coordinate-bearing artifacts

[abrignoni]

What

Audited every artifact that reports latitude/longitude and made sure they emit KML. The framework's kmlgen runs only when both are true:

1. 'kml' is in the artifact's output_types (note: "standard" excludes kml), and
2. the report has columns named exactly Latitude / Longitude.

38 artifacts had the coordinates but weren't producing KML. This PR fixes them:

35 — output_types only (already had exact Latitude/Longitude columns)

Enabled kml ("standard" → "all", or appended "kml" to the list). Examples: WhatsApp Messages, Health Workouts, all Apple Maps artifacts, 6× Uber, Threema/Zalo/Potato chats, Booking, Google Maps cache routes, Weather/WorldClock, Withings, life360 Chat, kleinanzeigen, swissmeteo, wire, photosDbexif, allTrails, cacheRoutesGmap, iOSCacheLocations, wifiNetworkStoreModel, foursquare Logs, uberLeveldb.

3 — single coordinate pair under a prefixed name → renamed columns + enabled kml

Artifact	Old columns	New
appleWifiPlist · WiFi BSS List	Location Latitude/Longitude	Latitude/Longitude
foursquareSwarm · Activity Feed	Venue Latitude/Longitude	Latitude/Longitude
uberClient · Uber - Account	Latitude (startup)/Longitude (startup)	Latitude/Longitude

(All three verified single-pair — no duplicate Latitude column results, so LAVA table creation is unaffected.)

Incidental lint hygiene

CI lints whole changed files, so two touched files needed pre-existing debt cleared:

• iOSCacheLocations: silence an intentional broad except (disable comment).
• wifiNetworkStoreModel: reindent tabs → 4 spaces. Logic and SQL unchanged (only whitespace).

Deferred (not in this PR)

• BeReal "Posts": blocked by a latent bug — process_bereal_preferences assigns the module globals bereal_user_id/_bereal_processed without a global declaration (the global is misplaced at module level), so they never update. That's a behavioral fix deserving its own review.
• Photos.sqlite Ph* reference tables (21): multiple coordinate pairs per row (zAsset/zExtAttr/Moment) — no single point to plot.
• Multi-pair artifacts: Withings Tracked Activities (start/end/center) and Apple Maps Trips (origin/destination) — ambiguous which pair to plot.

Verification

• AST-driven edits so only the coordinate-bearing function in each multi-artifact file was touched (never its siblings).
• All 26 changed files: pylint clean (no W/E/F), py_compile OK, structurally-changed modules import, no duplicate artifact names.
• CRLF line endings preserved on the two CRLF files (foursquareSwarm, iOSCacheLocations).