task/WG-321: improve how vector files are imported

[nathanfranklin]

Overview:

This PR along with Hazmapper PR migrates vector file ingest from "N features in PostGIS" to a "1 Feature + PMTiles asset" model.

Uploaded vector files (e.g. GeoJSON, shapefile) are reprojected to EPSG:4326, then the geojson is run through tippecanoe to produce a static .pmtiles archive, and stored as a single FeatureAsset (asset_type="vector") on a Feature. The pmtile is served directly to the client (over HTTP range requests).

Note: The GeoJSON-body endpoint for adding individual features (addGeoJSON) is unchanged.

Related Jira tickets:

• WG-321

Summary of Changes:

• TippecanoeService (geoapi/services/tippecanoe.py): wraps tippecanoe as a subprocess to build a .pmtiles archive from GeoJSON. Uses -zg to guess the max zoom, floored via --smallest-maximum-zoom-guess so sparse/large-extent data (which otherwise guesses zoom 0) still produces adequately-precise tiles. (Related reading is https://felt.com/blog/tippecanoe-display-scale-precision and https://medium.com/fika-blog/the-dark-art-of-vector-map-tiling-b417a3813df5)
• VectorService.convert_to_geojson (geoapi/services/vectors.py): reads any supported vector format via geopandas, reprojects to EPSG:4326, strips Z coordinates, extracts the bounding box, and writes GeoJSON to a temp dir. Defines SUPPORTED_VECTOR_EXTENSIONS; removes the now-orphaned process_shapefile.
• FeaturesService.fromVectorFile? converts to tippecanoe and then copies the .pmtiles into the project asset dir.
• Improve import of shapefile companion files (geoapi/tasks/external_data.py): the single-file Tapis import now lists the containing directory so only companion shapefile files that actually exist are fetched (avoids noisy 404s) ad non-required-file log downgraded to warning.
• Routes — the deprecated direct HTTP upload route rejects vector uploads with a 400 and points caller to the Tapis import endpoint.

Testing Steps:

1. Rebuild the worker image so tippecanoe 2.79.0 is installed (built from source in devops/Dockerfile.worker): docker compose build workers (or your local build target).
2. Use Task/WG-321: fix importing for geojson shapefiles hazmapper#481
3. End-to-end import: import a GeoJSON / shapefile / GPX from Tapis into a project
4. Check that it links back to original file in Designsafe

Notes:

• GeoPackage (.gpkg) — a multi-layer container (and can hold raster tiles), effectively "the 5 shapefiles users used to send, bundled." Our "1 file = 1 Feature" model would silently ingest only its first layer. Proper support means exploding its vector layers into N Features and surfacing any embedded rasters as internal tile layers. So this could be done later
• Improved styling

TODO

• file linking (original + current system/path) recorded on the vector asset
• add link to the hazmapper PR (client rendering + attribute panel)
• locally test scraping

[sophia-massie]

Nathan and I huddled - found with geoJSON with no metadata, the message "Click a feature on the map to see its attributes." could be confusing because its attributes will not appear after clicking.

Also noticed that the mouse isn't detecting that the pmtiles are clickable even though they are and work correctly i.e. change metadata depending on the point selected.