The camera‑module‑info.json is not used by the Web UI (camera metadata ignored)

[Mraanderson]

If your request is for a new camera support
Diagnostics were run on a Raspberry Pi Global Shutter Camera (IMX296). Picamera2 correctly identifies the sensor and exposes its capabilities. I added a proper IMX296 entry to camera‑module‑info.json, including the correct mode list and metadata. However, the Web UI does not use this information.

Is your feature request related to a problem? Please describe.
Yes. The file camera‑module‑info.json appears to be intended as the central place to define camera capabilities, but the Web UI does not consume it. Even after adding a correct IMX296 profile with valid modes, the UI continues to display the default IMX477/HQ camera settings. This means the metadata file has no effect on the user interface, and camera support cannot be added or extended through it.
This makes it impossible to support additional camera modules without manually editing HTML templates.

Describe the solution you'd like
I would like the Web UI to actually use camera‑module‑info.json when determining:
• available resolutions
• camera capabilities
• sensor‑specific settings
• UI labels and metadata
This would allow new cameras to be supported simply by adding an entry to the JSON file, without modifying templates or hard‑coded values.

Describe alternatives you've considered
I manually edited the HTML templates to match the IMX296’s real modes. This works, but it defeats the purpose of having a camera‑module‑info.json file. Another option would be to remove the JSON file entirely if it is not intended to be used. However, the ideal solution is to make the UI read from it so that camera support can be extended cleanly.

Additional context
camera‑module‑info.json contains detailed metadata for multiple camera modules, but none of this information is reflected in the Web UI. The UI instead uses hard‑coded values. This leads to inconsistencies between the backend (which correctly detects the camera) and the frontend (which ignores the JSON file). This affects all non‑IMX477 cameras and makes adding new camera support more difficult than necessary