Change Details

1. Try to copy a file from a random folder to the root folder of the GDrive. 2. Try to copy a file from a random folder to another random non-root folder on the GDrive. 3. Try to copy a file from a random folder to the same random folder on the GDrive, which creates another fileId with an identical originalFilename within that same folder. In all three cases, the FileCopyJob should succeed rather than throwing an error because the destination doesn't exist.

This bug is triggered whenever `KIOGDrive::copy` is called: 1. Try to copy a file from a random folder on the GDrive to the root folder of the GDrive. 2. Try to copy a file from a random folder on the GDrive to another random non-root folder on the GDrive. 3. Try to copy a file from a random folder on the GDrive to the same random folder on the GDrive, which creates another fileId with an identical originalFilename within that same folder. In all three cases, the FileCopyJob should succeed rather than throwing an error because the destination doesn't exist. Copying a file from a non-GDrive source into a destination on the GDrive uses `KIOGDrive::put` + `KIOGDrive::putCreate`, and copying a file from a GDrive source into a non-GDrive destination uses `KIOGDrive::get`, which is why the bug isn't triggered in these scenarios.

This bug is triggered whenever `KIOGDrive::copy` is called: 1. Try to copy a file from a random folder on the GDrive to the root folder of the GDrive. 2. Try to copy a file from a random folder on the GDrive to another random non-root folder on the GDrive. 3. Try to copy a file from a random folder on the GDrive to the same random folder on the GDrive, which creates another fileId with an identical originalFilename within that same folder. In all three cases, the FileCopyJob should succeed rather than throwing an error because the destination doesn't exist. Copying a file from a non-GDrive source into a destination on the GDrive uses `KIOGDrive::put` + `KIOGDrive::putCreate`, and copying a file from a GDrive source into a non-GDrive destination uses `KIOGDrive::get`, which is why the bug isn't triggered in these scenarios.