v1.11.0: add 138 Bosch + 48 Dahua cameras

[ch-bas]

What does this PR do?

• Bosch 22 -> 160 (+138): full active IP range from official Bosch datasheets cross-checked with netcamcenter.de — FLEXIDOME/DINION/AUTODOME/MIC + 42 thermal/fusion. Specs only where officially stated; empty otherwise (no fabrication).
• Dahua 107 -> 155 (+48): HDCVI analog, WizSense IP, WizMind, WiFi, PTZ from official dahuasecurity.com datasheets; added missing hdcvi protocol to 4 existing HDCVI cameras.

Database now covers 1,577 cameras across 68 brands.

Checklist

For new cameras

• JSON file is under cameras/<brand-slug>/<model-slug>.json
• id is a unique lowercase slug matching the file path
• brand, model, type, resolution are all present
• At least one URL in sources (manufacturer datasheet or reputable retailer)
• npm run build passes locally with no errors

For corrections

• Include a source URL confirming the correct value
• npm run build passes locally with no errors

For schema / tooling changes

• Existing cameras still validate (npm run build)
• Updated docs/glossary.md if new fields were added

---

Source(s)

All specs were referenced from official manufacturer datasheets, with distributor/catalog pages used only to enumerate the model list and corroborate values. Fields with no published spec were left empty.

Bosch (+138)

• Specs sourced from official Bosch:
  • https://commerce.boschsecurity.com / https://us.boschsecurity.com (official product pages)
  • https://assets.catalog.boschbuildingtechnologies.com (official datasheet PDFs)
  • https://resources.keenfinity.tech / https://commerce.keenfinity.tech (Bosch Building Technologies / Keenfinity — Bosch's official successor catalog)
• Corroborated with distributor spec pages where an official datasheet1securitycameras.com, use-ip.co.uk, sourcesecurity.com,

---

Dahua (+48)

• Specs sourced from official Dahua: https://www.dahuasecurity.com (official product pages + datasheet PDFs) — the primary source for every entry.
• Corroborated with distributor listings (sourcesecurity.com, etc.) where needed.

Each camera's JSON carries its specific source URL(s) in the sources field.