feat: add bulk upload of shapes

[meagharty]

Summary of changes

Asana Ticket: 🏹 Implement Shuttle Route KML Upload

• Adds /shapes_upload for uploading a file and extracting the LineString Placemarks
• Uses the "name" attribute in the KML file for each shape
• Adds coordinates to shape database from KML, the shape KML isn't valid without it anyway
• Edit page allows for update of the "name" of the shape within Arrow (not the filename, not the file contents, not the coordinates)

Currently redirects to /shapes on success.
Next iteration can include "and Shape Selection" from the ticket: to add the selection of only certain shapes from the KML and allow modification of their names.

Reviewer Checklist

• Meets ticket's acceptance criteria
• Any new or changed functions have typespecs
• Tests were added for any new functionality (don't just rely on Codecov)
• This branch was deployed to the staging environment and is currently running with no unexpected increase in warnings, and no errors or crashes.

[meagharty]

NOTE: I need to add a new migration for this change since the original scaffolding was already merged.

[bfauble]

does this need to be saved to the db as well as the kml file uploaded to s3?

[meagharty]

The designs for bulk upload for shapes is why I chose to include this in the db after all. There's versatility in having both the S3 files and the db representation of the coordinates.

It makes sense to have the kml files in S3 in terms of using the format used by other map/transit partners like Remix and Google Map (and gtfs_creator itself).

Since the ticket spec ended up calling for a bulk upload, with shape selection, shape re-naming, and coordinate consolidation, it seemed like making the backend aware (and able to later show/present) that data was worthwhile.

I see the concerns around the duplication though. What do you think?
cc @nlwstein @Whoops