refactor(api): remove legacy entity type in favor of kind

Why

Entity.kind is the canonical entity classification. The legacy multi-valued Entity.type field is no longer part of the product model, but API contracts and several callers still use it for catalog filters, entity creation, and presentation. This makes pages disagree about what an entity is.

API and data changes

• Replace the optional type filter on GET /entities with a kind filter using the entity-kind enum.
• Replace or remove the searchContext.type input where it represents entity classification.
• Remove type from entity create, update, detail, list, and search schemas.
• Remove the legacy database column and generated types through the normal migration workflow.
• Update the typed mock API and fixtures to use only kind.
• Keep bottle roles explicit on Bottle (brand, bottler, and distillers); do not reconstruct them from entity kind.

Web use

• /distillers requests kind=distillery.
• /brands requests kind=brand.
• /bottlers requests kind=bottler.
• Entity forms select one kind rather than several types.
• Entity detail presentation and contextual actions use kind only.

Acceptance criteria

• No public API entity contract exposes or accepts type.
• Entity catalog filters paginate and sort correctly by kind.
• Existing entities retain their canonical kind after migration.
• Bottle brand, bottler, and distiller assignments remain unchanged.
• The mock API covers distillery, brand, bottler, blender, and company records without a type field.

Start at the GET /entities API, the searchContext input, entity create/update/detail/list/search schemas, and the normal database migration workflow. Then trace the /distillers, /brands, and /bottlers requests and entity forms. Done means no public entity contract or mock fixture uses type, kind filters work, and bottle assignments and canonical kinds are preserved.