lineup-equipment-taxonomy

The **Available equipment** list in the lineup editor's sidebar is grouped by
equipment family, which is not how the planning team thinks about gear. They
want it grouped by our equipment taxonomy: first **Standard / House /
Non-Standard**, then **Electrical / Mechanical / Structural / Other** under
each.

I now have the mapping: `attachments/Equipment Taxonomy.xlsx` (the
`Equipment Taxonomy` sheet lists each equipment type specification with its
`Standard?` bucket and its `Category`).

The taxonomy belongs as columns on the `equipment_types` table, not in app
code. Equipment types already in the database get classified when the
migration runs, and anything the ingest brings in, through any of its import
commands, gets classified as it is imported. That includes the services API,
which ships as its own image built from `services/` alone.

The lineups equipment metadata API should return each equipment type's
classification as `standardBucket` and `disciplineGroup`, and the sidebar
should just group on the API response, with no normalization or fallback
logic of its own. Equipment the mapping doesn't cover still shows in the
list, under **Unknown**.

One more thing: on the final leaf rows, clicking the row should add it to the
block, instead of only the + button.

## Environment

PostgreSQL on localhost:5432 and the local database endpoint the app's
driver uses are running when you start, and the dev env files point at the
dev database.