Currently the CanMove rule implements its own logic separate from the of the DropConstraint. Since both classes deal with move actions we should try to reuse the latter from the former instead of duplicating the logic.

This should also solve the current problem with CanMove only receiving the first source item of a move action - even when multiple are selected.