Add Support for "Move Workspace File" API Endpoint

[neves-nvs]

Summary:
This pull request introduces an ad-hoc implementation to interact with an additional endpoint of the SendSafely API that is currently not supported by this package. The existing Python package for SendSafely does not expose this endpoint, so I’ve implemented the necessary functionality to support interactions with it. This was added based on our specific needs for file management within workspaces.

Changes Made:

• Added a new method to the Package class to interact with the previously unsupported "Move Workspace File" API endpoint.
• Added the corresponding exception class MoveFileException to handle errors related to this operation.

Notes:

• The additions are:

  • Package.move_file_to_directory(self, file_id, directory_id)
  • class MoveFileException
    These were named in alignment with the existing methods in the package. However, there are some inconsistencies across the documentation:
    • In the rest-api-docs.sendsafely.com - POST Move Workspace File, the endpoint is named Move Workspace File.
    • In the JavaScript Client for Node.js, the method for moving a directory within a workspace is named updateDirectory.

  These naming variations are noted for consistency with the rest of the package, but I believe the current names are clear and follow the existing patterns in the package.

[neves-nvs]

@SendSafely-GitHub I would like some feedback on this if possible.
@jhemler If there is any help you could provide, that would be appreciated.

Also, went to look into other packages:

• In developer.sendsafely.com/windows - ClientAPI Documentation - there exists ClientAPI.MoveFile(packageId, fileId, destinationDirectoryId) — So it is part of the SendSafely client object and not the Package object which in this client only exists as PackageInformation
• In developer.sendsafely.com/java - Documentation - there also exists a SendSafely.moveFile(String packageId, String fileId, String targetDirectoryId) throws FileOperationFailedException in SendSafely.java — So it is also part of the SendSafely client object

[hobelinm]

We tested internally

[SendSafely-GitHub]

Thank you @neves-nvs and @hobelinm. We have passed this on to our internal team that maintains the Python Client and will let you know once they review.