Move should act like bring when a move source is completely contained in a move destination #3054
Description
When you move a source to a destination and the ranges overlap, currently, move will throw an error, even if the move source is completely contained in the destination. In this case, however, the desired exchanges not really ambiguous. It would be a better user experience if move would behave the same as bring in this case.