Move items to a new path within a project

Paths are relative to `project/{projectId}/{visibility}`. Requires `canMoveCreatorItems` for `creator` and `canMoveReviewerItems` for `reviewer`. Items already in the destination folder are skipped (`count` may be 0). A destination inside a virtual folder is a copy, not a move, and costs the right of the matching add route: `Public/{token}/...` requires `canAddPubicFileSystemItems`, `Submission/{id}/...` requires `canAddSubmittionItems`, and dropping onto `Review/...` publishes the items (requires `canPublishAsset`). Those responses carry `virtualDestination: true` (and `published: true` plus `errors` for `Review/`).

curl -X PUT "https://example.com/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/files/creator/move" \  -H "Content-Type: application/json" \  -d '{    "itemPaths": [      "Renders/final.png",      "Renders/alt"    ],    "destinationPath": "Approved"  }'

{  "count": 1,  "virtualDestination": true,  "published": true,  "errors": [    {      "type": "string",      "message": "string",      "data": null    }  ]}