Add support for moving directories

I think the API should follow that for moving files.

• MoveDirectoryToDirectory(directoryPath, targetDirectoryPath) - Moves an existing directory to a new location (e.g. Move “build/project” to “package” results in “build/” and “package/project”). Target location must exist but full path to target location (once combined with directoryPath) must not.
• MoveDirectories(pattern, targetDirectoryPath) - Moves existing directories matching the specified patern to a new location. Actual move implementation as MoveDirectoryToDirectory.
• MoveDirectories(directoryPaths, targetDirectoryPath) - Moves existing directories to a new location. Actual move implementation as MoveDirectoryToDirectory.
• MoveDirectory(directoryPath, targetDirectoryPath) - Moves an existing directory to a new location, providing the option to specify a new directory name. Target location must not exist. (e.g. Move “build/project” to “package” results in “build/” and “package/” if “package” did not already exist and an error if it did, whereas move “build/project” to “package/project” results in “build/” and “package/project”).

I think the MoveDirectory API should only work for directories on the same volume. Alternatively, if we determine the targetDirectoryPath is on a different volume (not sure if there is an existing method for this?) then we could implement a method to create a new directory on the the target volume, move the files within that directory, recursively apply for any sub-directories, and then delete the source directory.

[daveaglick]

Going to submit a PR for this shortly. I’m only going to focus on the single MoveDirectory(DirectoryPath, DirectoryPath) alias. I agree with @RichiCoder1 that the other aliases performing multiple directory operations are troublesome.

As with File.Move(FilePath), I’ll create a Directory.Move(DirectoryPath) method to do the work that primarily defers to DirectoryInfo.MoveTo(string) so we’ll inherit it’s restrictions and semantics including the same volume restriction and the restriction on moving one directory on top of another.

[devlead]

Fixed by #1302