feat: add Windmill PBF export script to clip OSM data per sandbox project and upload to S3

[prabinoid]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Related to #7238

Describe this PR
Adds a self-contained Windmill Python script (scripts/export/pbf_data_export.py) that automates OSM data exports for active Tasking Manager projects.

On each run it:

• Fetches project boundaries from the TM active-projects API (or a static GeoJSON)
• Downloads a dated .osm.pbf from S3
• Builds OSM geometry tables (points/lines/polygons) in an in-memory DuckDB instance
• Clips each project to its boundary, applies tag filters per category (Buildings, Roads, Waterways, Landuse, Seamarks), and writes GeoJSON/SHP/KML outputs
• Zips and uploads results to S3 (or writes locally for testing)
• Supports two extraction engines (pure via ST_ReadOSM and quackosm) and adapts automatically to DuckDB MAP accessor semantics across versions. The script is designed to be dropped directly into Windmill with all parameters exposed as a typed form.

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud