Device provisioning

Factory or partner device provisioning flows

📄️HTTPS provision device (iotmer-auth-code)

Register a device or rotate MQTT credentials. Send the workspace **provision** API key in `iotmer-auth-code` (raw string; do not use `Authorization` on this route). Returns MQTT credentials and a one-time `device_http_token` for factory/device-side setup. Typical factory flow: `GET /provision/device-templates?workspace_id=...` (same header) → user picks a row → `POST /provision/device` with that row's `id` as `template_id`.

📄️List device templates for factory picker (iotmer-auth-code)

List assignable device templates for factory/device pickers (customer/public provision API). Send the workspace **provision** API key in `iotmer-auth-code` (raw string; do not use `Authorization` on this route). Query `workspace_id` is required and must match the key. Response is picker fields only (`id`, `scope`, `model_key`, `display_name`, `description`, `serial_format`). Use `id` as `template_id` on `POST /provision/device`. Empty `serial_format` means the client should send `device_key` when creating the device.