fix: bound space file ID matching

[fredrikblau]

Description

Space selection from a file ID currently uses an unbounded string prefix. When one space ID is a prefix of another, a file from the longer ID can resolve to the wrong space.

Match the complete space ID or the ! separator used before an item ID, and cover the prefix collision with a regression test.

Related Issue

• Fixes Vault unlock can mix up spaces with identical names in trash bin #3241

How Has This Been Tested?

• test environment: Node.js 26.7.0, pnpm 11.24.0
• test case 1: pnpm test:unit --run packages/web-pkg/tests/unit/helpers/spaces/driveAlias.spec.ts
• test case 2: pnpm check:types
• test case 3: pnpm lint
• test case 4: pnpm format:check

Types of changes

• Bugfix
• Enhancement (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt (improving code quality without changing functionality)
• Tests (adding or updating tests)
• Documentation (updates to the documentation, readme, or changelog)
• Maintenance (updates to the build process or auxiliary tools and libraries)

[JammingBen]

This doesn't fix the issue. fileId in getSpaceForDriveAliasAndItem is undefined for trash routes, which is the real issue. You need to pass it manually to the route like e.g. useSpaceActionsNavigateToTrash does.

[JammingBen]

👍