chore(trashbin): deprecate abortOperation on BeforeNodeRestoredEvent / switch to AbortedEventException

[joshtrichards]

• Resolves: #

Summary

Deprecates BeforeNodeRestoredEvent::abortOperation() to match the deprecation already applied to BeforeNodeDeletedEvent::abortOperation() and BeforeNodeRenamedEvent::abortOperation() in Nextcloud 29. BeforeNodeRestoredEvent was missed in that round.

Changes:

• Switched all three $event->abortOperation() call sites in files_trashbin's SyncLivePhotosListener::handleRestore() to throw AbortedEventException directly.
• Adjusted BeforeNodeRestoredEvent::abortOperation() to throw AbortedEventException internally (matching the files app's BeforeNodeDeletedEvent::abortOperation()), and marked it @deprecated.
• Added try/catch for AbortedEventException at the Trashbin::restore() dispatch site, consistent with how HookConnector::delete() handles it for the files app.

Fixes a bug: In the existing implementation, Trashbin::restore()'s if (!$run) check is dead code -- abortOperation() sets $run = false but immediately throws, so the exception unwinds past the check. The operation is aborted only because an uncaught exception propagates up the stack as an HTTP 500, not via the intended graceful return false path. This PR makes the abort mechanism work as designed + match its counterparts in the files app.

TODO

• ...

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