fix: handle missing parentheses in capabilities strings

[Guitou51]

Some monitors return a capabilities string with a missing closing parenthesis in vcp(...) or cmds(...). For example, the LEMON25 reports ... 62 87 8D CC mccs_ver(2.2)mswhql(1)), causing the parser to interpret mccs_ver as a hexadecimal VCP code and raise ValueError.

Stop numeric capability extraction at the next named field at the list's outer level. This preserves the supported codes, input sources, color presets, and metadata while keeping nested hexadecimal value lists intact.

Regression tests cover the exact LEMON25 response, its correctly closed equivalent, missing closures in both numeric lists, and nested values. Invalid numeric tokens still raise an error.

Validation: 136 tests passed; Ruff lint, formatting, and git diff --check passed.