Rename the equipment domain to machines; retype the models catalog (ADR-011)

The equipment plugin is now the machines plugin, ending the UI-vs-code
vocabulary split while the contract is pre-1.0 and nothing external
depends on the old names.

- plugins/equipment -> plugins/machines: manifest, class, /api/machines,
  machines.* permissions, registry key (with an auto-migrating load shim
  for existing installs).
- Tables: equipment -> machines (equipmentid -> machineid) and
  equipmenttypes -> machinetypes, renamed in the plugin's own migration
  chain (machines0002rename), idempotent for both upgrading and fresh
  installs.
- The legacy core machinetypes lookup actually types the vendor MODELS
  catalog, so it is renamed losslessly to modeltypes
  (models.modeltypeid, /api/modeltypes, Model Types settings page)
  rather than collapsed, freeing the machinetypes name. Core migration
  7d17_machines_rename also flips data in place: assettypes row
  equipment -> machine, auditlog entitytype, identifier_/search_
  settings keys, permission rows, and renames alembic_version_equipment.
- Frontend: machinesApi/modeltypesApi, item.machine response shape,
  assettype value compares 'equipment' -> 'machine' (map, search,
  custom fields, relationships), routes machines.js with plugin gating
  retagged, /print/machine-badge, Machine Types (subtypes) and Model
  Types (catalog) settings pages, machines-by-type report id.
- Docs swept; ADRs left as history per the authoring rule.

Upgrade: flask db upgrade then flask plugin upgrade-all.

Verified: dev DB flipped live (262 machines, 35 modeltypes, 95 models
retyped, zero equipment tables remain); fresh scratch-MySQL install
produces the new names; 341 tests green; naming/style green; frontend
builds; live E2E on machines list/detail, PC relationships, map,
reports, and both settings pages.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/PLUGIN-GUIDE.md

@@ -109,7 +109,7 @@ def meta(self) -> PluginMeta:
 The plugin owns two tables (`plugins/measuringtools/models/measuringtool.py`):
 
 - `measuringtooltypes` - the site-managed lookup (Caliper, Micrometer, ...) with a
-  display color, the same shape as `equipmenttypes` / `computertypes`.
+  display color, the same shape as `machinetypes` / `computertypes`.
 - `measuringtools` - the one-to-one extension of a core `Asset`, carrying only the
   metrology domain fields.
 
@@ -523,7 +523,7 @@ form is `requiresAuth`; the settings subtype page is `requiresAuth + requiresAdm
 **API client, addition only.** `frontend/src/api/index.js` gets a
 `measuringtoolsApi` object appended after `warrantyApi` (`list`, `get`, `create`,
 `update`, `remove`, `calibrationReport`, and a nested `types` CRUD). Do not
-reorganize the file; just add the block, mirroring `equipmentApi`.
+reorganize the file; just add the block, mirroring `machinesApi`.
 
 **Views mirror the master templates.** The frontend has master templates the
 frontend CLAUDE.md points to (`PrintersList.vue` for lists, `PrinterDetail.vue`