1. Summary
   Fix workspace move permission checks to use correct permissions in V2 mode.
2. Problem
   The workspace move operation was using incorrect permission checks for the target workspace in V2 mode.
3. Solution

• In V2 mode, use 'create' permission for target workspace instead of 'write'
• Add tenant-scoped existence checks for V1 admin moves
• Centralize target workspace access checks in the permission layer
• Refactor `WorkspaceAccessPermission` to handle different permission logic for V1 and V2
• Add helper methods to validate target workspace ID and check access
• Update error messaging for consistent 403 Forbidden responses

1. Testing

Added comprehensive tests covering various move scenarios:

• Admin vs non-admin users
• V1 vs V2 mode behavior

1. Expected Results

More precise and secure access control for workspace move operations across different access modes.