Page versions are lost when moving a page to another collective

Describe the bug
a page from collective 'A' when saved creates a version
if this page is moved into another collective 'B' the versions from collective A are lost.

To Reproduce
create collective A
add pages
add content to pages
modify content page and save to create multiple versions.
in our instance we had over 15 versions originally.

Create collective B
move page with versions from Collective A > Collective B
edit page to create more versions.
close browser and leave for a period of time
open browser > go to collective B > check versions if they are all still intact?

Expected behavior
for all versions to exist

Screenshots
ill upload screen shots into the next replay as i cant seem to add any here.
or you can grab the images from the below share up to the 26th June.
https://demo1nc.maxio.co/s/LoPFks4QfCQZjsB

Server details:

• Collectives app version: 2.18
• [Nextcloud Hub 10] (31.0.4)
• PHP Version: 8.1.29
• Database: 10.11.6-MariaDB

Client details:

• OS: Ubuntu
• Browser: Firefox (Floorp)
• Browser version: not sure its the latest flatpack
• Device: MS Surface Pro 8

{"reqId":"CfFTEgHAyeMInlXxVBQZ","level":3,"time":"2025-06-13T01:00:36+00:00","remoteAddr":"","user":false,"app":"PHP","method":"","url":"--","message":"rmdir(/var/www/nextcloud/data/admin/files_trashbin/files/collect.d1646989168): Directory not empty at /var/www/nextcloud/lib/private/Files/Storage/Local.php#123","userAgent":"--","version":"31.0.4.1","data":{"app":"PHP"},"id":"684b7cfb795f7"}

#### Browser log

</details>

Start by reproducing the reported steps: create versions in collective A, move the page to collective B, and inspect its versions after creating another version and reopening the browser. Trace the page-move and version-persistence entry points, using the supplied Nextcloud log for context. Done means all pre- and post-move versions remain available in collective B.