BDMS-783 -- add contacts to CSV Export on Map pages

[jeremyzilar]

What is changing

Map Export visible for water wells now produces a CSV whose column titles match the Ocotillo Wells list where the same field exists, with extra columns only for map export. Rows are enriched from thing/water-well/{id}/details when the feature has a numeric thing id. Column order is no longer driven only by alphabetical property keys: buildLayerCsv accepts a preferred key order so important columns lead the file. Optional VITE_OCOTILLO_PUBLIC_APP_URL documents how to control the Well detail page link base in exports.

What changed

• src/well-list/wellListColumnLabels.ts
  Single source of truth for DataGrid headerName strings on the water well list and for shared map CSV headers.

• src/utils/wellPublicUrls.ts
  Helpers to build absolute well show URLs (default production host; override via env).

# Optional: base URL for well detail links in map CSV export (defaults to https://ocotillo.newmexicowaterdata.org)
# VITE_OCOTILLO_PUBLIC_APP_URL=https://ocotillo.newmexicowaterdata.org

• src/well-export/wellMapCsvExport.ts
  Map CSV label maps (WellListColumnLabels + WellMapCsvOnlyLabels), preferred header order, row builder (buildWellMapCsvValues), enrichment-failure row, site name resolution (API, OGC site_name, Unknown alternate IDs), and cleanup of legacy detail_* / redundant OGC id fields on features.

• src/utils/layerExport.ts
preferredPropertyColumnOrder: emit those property keys first (when present), then remaining keys sorted A–Z, then geometry columns.

• src/utils/wellMapExport.ts
  Batches fetches to thing/water-well/{id}/details and merges flattened CSV fields into each feature’s properties for export.

• src/pages/ocotillo/thing/list.tsx
  Well list columns use WellListColumnLabels for headerName values.

• src/pages/ocotillo/map/list.tsx
  Export path uses buildMapExportPreferredColumnOrder() and enrichMapFeaturesWithWellDetails.

• src/components/WellShow/Contacts.tsx
  Contact block uses inline caption text again (not shared export constants) so the well detail UI stays independent of CSV label modules.

• .env.production.example
  Comment block for optional VITE_OCOTILLO_PUBLIC_APP_URL.

How to test

1. Wells list (thing/list): confirm grid headers match expectations (same strings as WellListColumnLabels).
2. Map, water well layer, select an area, Export visible: open CSV and check:
   • Well ID, Name, and other shared fields use the same titles as the list.
   • Well detail page URLs are correct; with VITE_OCOTILLO_PUBLIC_APP_URL set, links use that origin.
   • No stray detail_* columns or duplicate OGC id columns if you saw them before.
3. Optional: set VITE_OCOTILLO_PUBLIC_APP_URL locally, rebuild, re-export, confirm link host.

[github-actions]

Preview Deployment

Preview URL: https://preview-bdms-783-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.