Add Move behavior for Copy activity in Fabric pipelines

[arpost]

Pipelines are really handy low-code ways to manage file movement, but the lack of a true Move option in a Copy activity makes pipelines incredibly CU-heavy when it comes to large numbers of files. This is due to Copy...well...copying files rather than using Microsoft's file system APIs to change metadata like you can do in Fabric notebooks with utilities.

Please add a Move option that doesn't duplicate files but instead changes their metadata so files don't have to literally be duplicated.