Allow User Gesture Requirement for Custom Visualization Mods to be Configurable

Mods API 2.4 requires a user gesture (like a click) before AnalysisProperty.set() can write a document property. This blocks any mod that needs to write a property based on a value that only becomes known asynchronously, from streaming data, a loaded dataset, a callback, or any other non-interactive event, since there's no user click naturally tied to that moment.

Two workarounds are adding a UI element whose only purpose is to manufacture a qualifying gesture, or adding a script on navigate that bypasses the requirement. Both add UI clutter or analysis bulk, and the button approach depends on the user remembering to interact with it, all of which significantly affect UX.

A fix we'd like to see is making this user-gesture requirement configurable at the server, analysis, mod, or property level by an admin or mod author. Known risk: relaxing it opens up potential issues with the undo/redo queue, since writes without a tied user action have no clear point to undo back to, so this should be treated as a deliberate, documented tradeoff rather than a default.