Missing Spatial Indexes and errant capital planning database elements

[TangoYankee]

Description

There are a few typos and missing features for the capital planning database. We should clean these up as part of the same migration.

Acceptance criteria

• [x] The captial_commitment table is renamed to capital_commitment #248
• [ ] The third option of the capitalProjectCategoryEnum is changed from ITT, Vehicles and Equipment to ITT, Vehicles, and Equipment (add oxford comma)
• [x] The community_district.li_ft column type is changed from multiPointGeom to multiPolygonGeom #247
  • bonus ticket- rename the file so that "community" has the correct number of 'm's fixed in #286
• [x] spatial indexes are added to the columns:
  • [x] capital_project.mercator_m_pnt
  • [x] capital_project.mercator_m_poly
  • [x] community_district.mercator_fill
  • [x] community_district.mercator_label
  • [x] city_council_district.mercator_fill
  • [x] city_council_district.mercator_label
• [x] nullablity is reviewed and addressed

Context

Enum

Postgres does not allow the modification or removal of items from an enum. Instead, we need to do a wholesale replacement of the enum.

Indexing

PostGIS Spatial Indexing is done "using GIST". Drizzle ORM support writing indexes with the "using" keyword. However, drizzle-kit (which generates the migration files) does not. We'll still use drizzle-kit to generate the migration. However, we'll then hand-edit the migration file to use "GIST"

Related work

Blocked by writing the ETL. It's pointing out more errors as data are added. We should get the ETL finished to help identify more errors that we can include in this migration.

[TangoYankee]

This was originally conceived as a big ticket item where we consolidate the errors into a single migration. This was misguided. We should be making these adjustments in small migrations. Going forward, I'm also going to try adding these changes into the endpoint implementation into the tickets that will need them.