list_properties() and list() methods #4557
Description
Considering the change holistically from the server API onward, could this introduce more complexity for external developers constructing clients, particularly those handling settings APIs generically across products like Fluent, CFX, etc.?
I’m wondering whether moving these commands to the root level makes sense in the broader context of the settings API as a potential cross-product blueprint.
From a trade-off perspective, is the reduction in static info size the primary motivation, or do we expect additional tangible benefits that offset the added indirection?
Originally posted by @seanpearsonuk in #4398 (comment)