fix: Skip unsupported KML NetworkLinks instead of failing the whole import

[njakobsen]

Problem

A KMZ exported from Google Earth that mixes embedded placemark geometry with <NetworkLink> elements (links to remotely hosted layers) failed to import entirely, surfacing only a generic "Unable to import features due to a map data error." Importers::KML#kml_document raised ImportError on the first NetworkLink it found.

Reported by Michelle from Ktunaxa: her BC Hydro Facilities IVMP.kmz contains 133 importable points + polygons plus 2 NetworkLinks (Substations, Mobile Radio Repeaters), and imported nothing.

Change

• Importers::KML now strips NetworkLink nodes and records a non-fatal warning naming the skipped layers, then imports the embedded geometry.
• New warnings accumulator on Importers::Base; aggregated in update_features! and persisted to spatial_processing_status_cache (read via feature_update_warnings) so they survive job completion (successful Delayed::Jobs are deleted).
• Each warning is prefixed with its importer's source_identifier (e.g. archive.zip/layer.kml), so a multi-file / multi-source import identifies which file the warning belongs to.
• A NetworkLink-only file still fails, but now via EmptyImportError whose message explains which layers were skipped.

This preserves the original 2023 intent (fail loud when a file has nothing importable) while no longer discarding valid geometry.

Validation

• Full spec suite green (added importer + update_features! coverage, a hybrid fixture, and a multi-file attribution test).
• Reproduced end-to-end against the real importer under the Ktunaxa deployment: her KMZ now imports all 133 features (112 points, 21 polygons) and persists the (file-attributed) warning. (Validated on the equivalent 3.9.x build, since the consuming connect_engine pins ~> 3.9.0; the NetworkLink code path is identical on master.)

Downstream (toward Stolo/SC)

connect_engine surfaces these via a companion PR (specific reason on failure + warning notice on partial import). On a Referral / ReferralSubmission the warning renders as an in-page notice via feature_update_notifications, since those models import the footprint directly (include UploadedFileMapLayer). To reach deployments, CE's spatial_features pin needs to allow 3.10.2, then CE + SC bumps follow.

🤖 Generated with Claude Code