Make a perf-focused command that removes a lot of the guard rails that a normal orogene installation would do, on the assumption that orogene is running in a much safer, controlled environment and doesn't need to compensate for a lot of bad shit.

Some ideas:

• Skip pruning
• Error if node_modules already exists
• Write directly to cacache content dir, without the tempfile -> move dance
• Disable integrity verification for extracting files from the cache (we assume the cache won't get corrupted, and if it does, it'll be handled separately)
• Only works if lockfile + package.json are in sync. Errors otherwise.
• Skip writing to log file (you'll need to set verbosity by hand in CI)