Rethink the trigger delay modifier semantic for multiple event targets

Similar to #2891, the delay modifier behaves suboptimal when multiple nodes can provide data. I think the desired behavior here is also to have one shared delay per trigger specification. I.e. going with the active search example again, if I have two form elements `name` and `city`, as long as I change either value within the delay, the trigger shouldn't be activated.