This work prepares for `turbopack build` by extracting code common between dev and build, such as asset context.

This also makes the cli accept a variadic list of entries rather than an unnamed directory parameter. The project directory is now available under `--dir` or `-d`.

Test Plan: `cargo run -p turbopack-cli dev` with a `src/index.js` present and `cargo run -p turbopack-cli dev src/entry.js` with `src/entry.js` present.

Depends on #5487

This implements a basic version of `turbopack build`, only targeting browser targets. In the future, we could accept a cli or configuration option to target Node.

Test Plan: `cargo run -p turbopack-cli build` with a `src/index.js` present and `cargo run -p turbopack-cli build src/entry.js` with `src/entry.js` present.

…e-cli

… wbinnssmith/turbopack-cli-build

…i' into wbinnssmith/turbopack-cli-build

…rize-cli' into wbinnssmith/turbopack-cli-build

…e-cli

… wbinnssmith/turbopack-cli-build

…dularize-cli

…mith/modularize-cli

…e-cli

…dularize-cli

… wbinnssmith/turbopack-cli-build

…i' into wbinnssmith/turbopack-cli-build

…mith/modularize-cli

…e-cli

…dularize-cli

… wbinnssmith/turbopack-cli-build

…-cli-build

…rbopack-cli-build