turbopack-cli: Use correct fs and env for builds (#73487)
This fixes two issues with resolving for turbopack-cli in builds:
- Builds used the `output_fs` in the `ResolveOptionsContext` resolve
origin, so node_modules were never found as the lookup path could never
be in the same filesystem as the root path [0]. It now uses
`project_fs`.
- Production used the `development` custom condition. It’s now
`production` and `browser` is added by default.
[0]
https://github.com/vercel/next.js/blob/8756f7a65bd9922b3bb90050ee225c8bcdf6a535/turbopack/crates/turbopack-core/src/resolve/mod.rs#L1302
