movingWallVelocity allows non-zero input in case of static mesh
In case of non-moving the only value that makes sense is (0 0 0). Can we enforce this as per noSlip? Or do we re-interpret the value as a relative, additional motion in which case the moving() functionality should account for that.