next.js

39e705ca - Turbopack: Merge release-with-assertions-no-lto profile into release-with-assertions (#91530)

Turbopack: Merge release-with-assertions-no-lto profile into release-with-assertions (#91530) - More profiles means more bloat to the `target` directory and more cold builds. - There's no practical use case where we'd be okay with the performance hit of `debug-assertions` and not okay with the performance hit of `lto = false`. Neither profile was suitable for benchmarking. - `release-with-assertions-no-lto` is too long to type and was giving me carpal tunnel.