Support uploading model runs from the web client

[floryst]

Add support for uploading model runs from the web client.

This draft PR gets the end-to-end pipeline of uploading and processing a zip file of geojsons. There are a couple of extra things to do to complete this PR.

• [x] Cleanup the UI
• [x] Enforce certain validations on the UI (e.g. not allowed to submit without a title)
• [x] Send the private flag, and apply the private flag on the backend
• [x] Run code linter
• [x] Address the TODOs

The core pipeline can use an initial review pass.

Screenshots:

[floryst]

@BryonLewis is there an existing notion of a private/public model run in RD-WATCH?

Bryon: No there isn't. I've added fields to the Region and model-run endpoints to indicate if a item is public (it defaults to true). I haven't done any filtering or sorting on those fields yet (except maybe custom regions).

[floryst]

Recent updates:

• use django-s3-file-field with s3 in prod, minio in dev
• properly type the VFileInput model value
• skip originator validation in SiteFeature. This is necessary because ingested geojsons may have originators that are not yet in the database. We can safely skip this check because we will add the missing performers later before saving the model run.
  • side note: the implementation would be better with pydantic v2 contexts
• refresh the performers and regions when a successful upload occurs

[floryst]

This PR now depends on #502 and #503.