fix: check source and target when emitting copy event

[salmart-dev]

Summary

Fixes an issue when updating files using the ChunkingV2Plugin plugin if the source file and the destination file reside on different storages.

The issue appeared since #52996. After that PR we attempt emitting an FS copy event hook where the source path resolves to null since its absolute path is not in /USER/files but in /USER/uploads. Since the plugin already takes care of emitting the update event, the copy one should probably be skipped.

The bug causes the following exception:

│[ERROR] 2026-03-02T12:08:18+00:00 chz 192..21.2 webdav     
  OC\Files\Node\HookConnector::getNodeForPath(): Argument #1 ($path) must be of type string, null given, 
called in /var/www/html/lib/private/Files/Node/HookConnector.php on line 188            
   TypeError: “OC\Files\Node\│

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[come-nc]

I think your fix makes sense.

The Node API does not support files outside of files/ folder anyway (and that’s what we are moving towards, events are supposed to be replaced by events, using nodes).

It was always a grey area for me when source is in files and not target (or the opposite) what should happen.

[susnux]

Makes sense!

[salmart-dev]

/backport to stable33

[salmart-dev]

/backport to stable32

[salmart-dev]

/backport to stable31

[salmart-dev]

/backport to stable30

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/58660/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 8431abff

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/58660/stable30

Error: Failed to push branch backport/58660/stable30: remote: Invalid username or token. Password authentication is not supported for Git operations.
fatal: Authentication failed for 'https://github.com/nextcloud/server.git/'

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.