[AlexAndBear]

Description

• Navigate after moving the current folder: moving the folder you are in (breadcrumb menu > Move to) only removed it from the list, so the view stayed on a path that no longer exists and creating a folder there failed with 409. When the current folder is among the moved items, the view now navigates to its new location, like rename and delete of the current folder already do.
• Route built from the source space: the move only happens within one space, and the target from the location picker is a plain object without methods at a project space root, so the route is built from the source space.

Related Issue

• Fixes Moving the current folder leaves the view on a path that no longer exists #3868

How Has This Been Tested?

• test environment: unit tests (Vitest), browser tests (Playwright) against a local OpenCloud
• test case 1: unit: moving the current folder navigates to its new location, also into a project space root; moving another item or copying across spaces does not navigate (the regression tests fail without the fix)
• test case 2: browser: breadcrumb Move to: main stayed on the old path and MKCOL failed with 409; with the fix the view and breadcrumb follow to the new path and creating a folder works (checked via WebDAV)
• test case 3: browser: keep both lands in the renamed folder, move into a project space root and subfolder, a failed move (500) does not navigate
• test case 4: browser: moving a normal item, cross-space copy, rename and delete of the current folder behave as before

Types of changes

• Bugfix
• Enhancement (a change that doesn't break existing code or deployments)
• Breaking change (a modification that affects current functionality)
• Technical debt (addressing code that needs refactoring or improvements)
• Tests (adding or improving tests)
• Documentation (updates or additions to documentation)
• Maintenance (like dependency updates or tooling adjustments)