Fix Turbopack production builds for evaluation-only dynamic imports. An import such as `const {} = await import('../pure')`, where the imported module is side-effect free and no exports are consumed, must not leave the build referring to code that tree shaking removed: the build should succeed and the unused module should be absent from the emitted server output.

Apply the same behavior to dynamic import patterns such as template-literal requests. A pattern can resolve to multiple modules with different side-effect characteristics, so each resolved target must be handled independently: omit side-effect-free, evaluation-only targets while retaining targets whose evaluation has observable effects. Dynamic imports whose exports are actually consumed must continue to load normally.