storage-site-linking

From the storage team:

> Some storage master notes:
>
> - Can we add an Active / Inactive field for us to manually indicate if the
>   location is still operational?
> - We're not there yet from a data perspective for this to be accurate, but
>   I think it would be useful to give summary numbers by location:
>   - Total value of equipment in storage
>   - \# of pieces of equipment in storage
>   - hidden columns that break both of these out by equipment type would be
>     awesome (picturing a small number of columns with commonly stored
>     prebought equipment types and then an "other" bucket to catch
>     everything else)
> - Eventually I want to use the list similarly to the equipment list to do
>   data validation in the Equipment view – you can't enter a storage
>   location that doesn't exist in the storage master. Once you enter the
>   name, the address and any other related fields autopopulate
>   - To work on getting there, maybe we add a "Storage Site Name" column to
>     the Equipment table, autopopulate it based on the address we already
>     have listed where we're able to (suspect unfortunately won't be too
>     many cases) and then we'll get in and fill out the remaining names?
>     Lmk your thoughts if there's a better approach

Let's do all of it now, the "eventually" part included: Equipment gets a
Storage Site that can only be a location from the storage master (Settings →
Storage Locations), and choosing one fills in the equipment's Current
Address. When the team corrects a location's address in the master, the
equipment linked to it should show the corrected address. Keep the existing
free-text Storage field on Equipment as it is.

For equipment already in the app, link each row whose Current Address is one
of the master's addresses. Those addresses were typed by hand, so the same
place often differs only in capitalization, punctuation or abbreviation
("Avenue"/"Ave", "North"/"N", "Texas"/"TX"). Don't guess, though: an address
that could be more than one location stays unlinked for the team to fill in.

A location that still has equipment linked to it shouldn't be deletable —
they'll mark it Inactive instead.

The API shape for the new totals, and the names of the new fields, are
already in `web/src/api/storage-locations/storage-equipment.schema.ts`.

## 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.