What version of Turborepo are you using?

1.3.1

What package manager are you using / does the bug impact?

Yarn v2/v3 (node_modules linker only)

What operating system are you using?

Linux

Describe the Bug

The _metadata: version identifier is hard-coded to be 5 in the turbo prune command, however the latest version of yarn uses 7. This may cause yarn to not identify a yarn.lock file generated by turbo prune as valid.

Expected Behavior

turbo prune should generate a lockfile with the version, based on the current version of yarn being used.

To Reproduce

1. Run turbo prune. Lockfile generated will have 5 as the version.
2. Try to run yarn install and yarn will not recognize out/yarn.lock and will try to generate it's own. Additionally, this means .yarn/cache cannot be used.