Fix plain object storage move directory operation undo

[Michicosun]

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Do proper undo of the move directory operation in case of error. We need to rewrite all prefix.path objects changed during the execution, not only the root one.

[clickhouse-gh]

Workflow [PR], commit [d891f81]

[tuanpach]

Could you give some explanation about the bug and the fix of this change?

[antonio2368]

This is a bugfix so it needs changelog.

[Michicosun]

Could you give some explanation about the bug and the fix of this change?

For example, if you have this tree

├── __meta
│   ├── jgtebynqegaurjaqegmluoztzyhnuxfr
│   │   └── prefix.path 
│   │       └── xl.meta A/B/C/G/
│   ├── qfyudsrpexcaikpgnpvfppjvyskkbhqg
│   │   └── prefix.path
│   │       └── xl.meta A/B/
│   ├── vajvgtqqpluxgbstacyeuprihfvxpbzi
│   │   └── prefix.path
│   │       └── xl.meta A/B/D/
│   ├── vqmufevphfeqbetdniedzqimqbwpraey
│   │   └── prefix.path
│   │       └── xl.meta A/
│   ├── wnygkhaxgcruzpmxtmzoaknnmaeorvds
│   │   └── prefix.path
│   │       └── xl.meta A/B/E/
│   └── yaillkbvcggwapggvstxwjbvgiqfzruh
│       └── prefix.path
│           └── xl.meta A/B/C/

And you execute moveDirectory('A', 'MOVED'); moveFile('non-existing', 'other-place'), then the tx will fail, because the non-existing file does not exist, but during the undo of the first operation, only the root folder (in this case 'A') will be moved back, but A/B will not.

Though here is another problem, move directory renames only the first level folder, which means in the example ^ only A/ and A/B/ will be changed, but not the whole subtree, but I will fix that in another PR.

[Michicosun]

Waiting for #88240 to be able to extend with tests and change the changelog entry to bugfix