Add File Move Operation to PATCH Endpoint

[duquesnay]

Summary

Adds file move operation to the PATCH endpoint, allowing files to be moved within the vault while preserving internal links.

Dependencies

• Depends on PR feat: Add file rename functionality via PATCH /vault/{filepath} #176 (file rename) - must be merged first

Changes

• Add move operation to PATCH endpoint for files
• Implement handleMoveOperation method
• Add path traversal security validation
• Add 8 test cases covering success and error scenarios
• Update OpenAPI documentation
• Refactor PATCH validation logic

Security

• Blocks path traversal attempts (../)
• Rejects absolute paths
• Validates and normalizes all input paths

Usage

curl -X PATCH https://localhost:27124/vault/old/path/file.md \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Operation: move" \
  -H "Target-Type: file" \
  -H "Target: path" \
  -H "Content-Type: text/plain" \
  -d "new/location/file.md"

Implementation

• Uses FileManager.renameFile() to preserve links
• Creates parent directories as needed
• Returns appropriate error codes and messages
• Follows existing error handling patterns

[coddingtonbear]

I think this PR might be a good solution for the concerns I had around #176 so I think this is worth talking over more!

This PR, though, looks like it includes all of the changes of both #176 and this PR rather than being just the unique work for this particular problem. To make this PR reviewable, what you need to do is set its base branch to be the branch you made for #176 rather than main.

[j-standfast]

a) coddingtonbear - thanks for this plugin; it's great and much needed
b) duquesnay - thanks for this timely PR; I was about to take a stab at implementing exactly this functionality, only to discover you'd just done it; it too, is much needed
c) I'm now running a build from this PR and so far, so smooth - intuitive, running as expected, etc. etc.

no notes

[coddingtonbear]

I talked this over briefly with @duquesnay and I'm suggesting to him that he approach this via creating an API extension as the first pass. See https://github.com/coddingtonbear/obsidian-local-rest-api/wiki/Adding-your-own-API-Routes-via-an-Extension for insight into what that might look like.