Expand integration test coverage for WS commands

[markvp]

Problem

Only ~5 of ~40+ WS commands have integration test coverage. Most handlers are untested end-to-end:

• device_command, read_attribute (beyond basic), ping_node
• get_matter_fabrics, remove_matter_fabric
• set_acl_entry, set_node_binding
• check_node_update, update_node
• discover_commissionable_nodes
• set_default_fabric_label
• get_loglevel, set_loglevel
• Error cases (InvalidArguments, NodeNotReady, NodeNotExists)

The existing integration tests also have pre-existing failures on Windows (BigInt conversion issue cascading from commissioning).

Proposal

Systematically expand IntegrationTest.ts to cover all command handlers, including both success and error paths.

Labels: testing, enhancement

[Apollon77]

I am not sure tbh ... several of the methods are just doing a read ow write or invoke which are basic functions. Please create an own issue for the "pre-existing failures on Windows (BigInt conversion issue cascading from commissioning)" faailure.

[markvp]

It was a library install issue because I'm on Windows ARM. If you're moving away from BigInt conversions I'll wait and see if it remains a problem. It's only a development environment issue, not a runtime issue.