Fix ESRIGeoJSON: handle Empty reply from server and paginate past maxRecordCount

[rywall]

Summary

• Empty reply from server: ESRIGeoJSON passed remote URLs straight to ogr2ogr, which uses GDAL's curl client. Some ArcGIS-on-IIS endpoints return an empty reply to that client (likely an HTTPS 1.1 negotiation issue — GDAL's driver list hints at this with MapInfo File' needs https 1.1), producing ERROR 1: Empty reply from server. Fix: fetch the URL with Ruby's `open-uri` into a tempfile, then run `ogr2ogr` on the local path.
• Truncation at maxRecordCount: ArcGIS query endpoints cap each response at the service's `maxRecordCount` (commonly 1000 or 2000 features) and signal `exceededTransferLimit` when more results exist. Fix: walk the pages with `resultOffset` and merge them into a single FeatureCollection before handing to `ogr2ogr`.
• Local-path behavior is unchanged.

Test plan

• Import features from an ArcGIS-on-IIS REST `query?...&f=geojson` URL that previously failed with `Empty reply from server`.
• Import features from an ArcGIS query URL whose result set exceeds `maxRecordCount` and confirm all features are returned (not just the first page).
• Import features from an ArcGIS query URL whose result set fits in one page and confirm a single request is still made.
• Import features from a local `.geojson` / `.json` file (regression check for the relative-path branch).

🤖 Generated with Claude Code