Auto-play inconsistency: controller state-setter helpers restart the render loop, while ViewModel*Property updates (Boolean/Number/Trigger/…) do not

Description

rive-android offers two main ways to drive a State Machine at runtime:

With autoplay = false (or after view.pause()), a controller helper immediately shows the change, whereas any ViewModel*Property update has no visible effect until the render loop is restarted manually (riveView.play() or controller.requestAdvance()).
This asymmetry forces developers to add extra code only for ViewModel properties, which is error-prone.

Reproduction

class ReproActivity : ComponentActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        val rive = RiveAnimationView(this).apply {
            setRiveResource(R.raw.machine_demo) // State Machine has Boolean "flag" and Trigger "pulse"
        }
        setContentView(rive)

        // 1️⃣ Controller helper → immediately visible
        rive.controller.setBooleanState("machine", "flag", true)

        val vmi = rive.controller.activeArtboard!!.viewModelInstance

        // 2️⃣ ViewModelBooleanProperty → no visible change
        vmi.getBooleanProperty("flag")?.value = false

        // 3️⃣ ViewModelTriggerProperty → no visible change
        vmi.getTriggerProperty("pulse")?.trigger()
    }
}

Any .riv exposing a Boolean input flag and Trigger input pulse, both bound through the State Machine and the ViewModel, reproduces the issue.

Expected behaviour

All public input APIs should follow one consistent contract:

Device & versions

Start with the controller state-setter helpers and the ViewModel Boolean, Number, String, Enum, and Trigger property updates described in the issue. Reproduce with autoplay disabled or after pausing the view, then determine which consistency option is accepted; done means both API families follow the selected contract and the reproduction behaves consistently.