Data extracts from raw-data-api should always be downloaded, update project creation workflow

[spwoodcock]

• When we create a data extract via raw-data-api, we should not treat this as special as we do currently:
  • We authenticate with raw-data-api (one extra layer of complexity for administrators of FMTM aside from HOT), plus link directly to the raw-data-api flatgeobuf URL in the S3 bucket.
  • Instead we should simply transfer this file to our bucket, with the bundled Minio instance as part of FMTM (or to the remote attached S3 bucket).
  • This way all data extracts are in the same place, and all treated the same.
  • Originally raw-data-api was the primary data source of FMTM, but now we should treat it as a data source option (one of many).
  • During project creation create extracts as normal and display on the frontend, but save the last extract URL that was created.
  • During project submit, send EITHER raw-data-api parsed GeoJSON, or the custom data extract GeoJSON to the same endpoint for upload.
  • The endpoint should upload the geojson as flatgeobuf to our S3.
  • Delete env var param RAW_DATA_API_AUTH_TOKEN references?