component.Base: promiseVdomUpdate() => honor the silentVdomUpdate state

I have been chasing down this one for quite a while.

When calling component.set() or manually locking a cmp for updates, most afterSet() methods are using me.vdom = vdoM;.

However, there are spots where I am using me.promiseVdomUpdate() instead to use the callback.

Those calls were bypassing the silent flag, which can trigger additional delta engine calls. The mean thing is that in those cases, the new vnode is not in place yet (the engine works async inside the vdom worker), which can lead to duplicate dom updates and result in errors.