autoSelect/autoUpDown have no backend hook for a module to react to grid selection/reorder

PropertyMulti::autoSelect()/setAutoSelect() and autoUpDown()/setAutoUpDown() (libs/model/property/propertymulti.h/.cpp) are settable flags with no wiring beyond their own getter/setter - never dumped to the client (PropertyJsonDumper never reads them) and never read anywhere else server-side either. Confirmed by grep: zero usage beyond the plain accessor pair.

These flags are not meant to control the frontend directly (the generic grid UI in ostcore already shows edit/up/down/delete/row-click controls unconditionally whenever a grid property is editable - that part is working as intended and is not the gap). The actual gap is backend-side: a module developer has no way to hook into what should happen when a user selects a grid row (autoSelect) or reorders one (autoUpDown) - no virtual method, no event, nothing PropertyMulti/Basemodule exposes for a module to run its own logic at that moment.

Found while documenting the grids/graphs chapter of the dev-module series (issue #264 (closed)).

No proposed fix shape yet - needs real design thought (what the hook signature should look like, whether it is a new virtual on Basemodule like onOtherModuleEvent(), or something else). Deliberately deferred, not urgent.