turbo

6cc16540 - test: Add lockfile fixture for yarn berry resolution pruning (issue #2791) (#12071)

test: Add lockfile fixture for yarn berry resolution pruning (issue #2791) (#12071) ## Summary - Adds `berry-resolution-full` lockfile test fixture covering yarn 3 resolution handling during `turbo prune`, as reported in #2791 ## Context Issue #2791 reported that `turbo prune` produced broken lockfiles for yarn berry monorepos when the root `package.json` contained a `resolutions` field. Resolved transitive dependencies were silently dropped from the pruned `yarn.lock`, causing `yarn install --immutable` to fail. This was fixed in #4684 (Rust berry lockfile implementation) and refined in #4770 (patch descriptor filtering). The fixture ensures this regression doesn't recur. Closing #2791 with this PR. ## Fixture details The fixture uses yarn 3.6.0 with a `resolutions` override (`is-number: ^7.0.0`) where `is-odd` transitively depends on `is-number@^6.0.0`. This forces the lockfile to resolve via the override rather than the original specifier -- the exact pattern that triggered #2791. Both workspace prune targets (`web` and `@repo/ui`) pass on the current turbo binary.