Introduce ENSO_LAUNCHER env var to configure behavior of buildEngineDistribution

[Akirathan]

Closes #12014

Pull Request Description

Introduce ENSO_LAUNCHER env var that configures if and how the native image of engine-runner is built (More specifically, how sbt buildEngineDistribution command behaves):

• native: NI is built optimized without assertions and without debugging symbols
• debugnative: NI is built not-optimized with assertions enabled and with debugging symbols.
• shell (the default value): NI is not built - buildEngineDistribution continues to behave as on develop.

Docs in native-image.md

Important Notes

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[Akirathan]

The Engine Checks CI job uses ENSO_LAUNCHER=debugnative (https://github.com/enso-org/enso/actions/runs/12747958886/job/35527132108?pr=12035#step:7:727), all the other jobs either set ENSO_LAUNVCHER=shell explicitly (like JVM Tests here), or don't set ENSO_LAUNCHER env var at all, which will fallback to shell.

I believe this PR is ready to be merged.

GitHub

Introduce ENSO_LAUNCHER env var to configure behavior of buildEngineDistribution · enso-org/enso@fb9e94d

Enso Analytics is a self-service data prep and analysis platform designed for data teams. - Introduce ENSO_LAUNCHER env var to configure behavior of buildEngineDistribution · fb9e94d

[JaroslavTulach]

• please remove CHANGELOG entry - this is not end user visible change
• I would avoid setting ENSO_LAUNCHER when default value is needed in the CI scripts

[hubertp]

additionalOptions.. additionalOpts.. additionalFoo. This is getting confusing.

[Akirathan]

A bit. One is a parameter to the method, and the other one is a value from the task. I don't know now how to merge these two, with minimal changes.

[JaroslavTulach]

Looks like the CI is green:

• there are two GraalVM Native Image: Generating enso messages in the Linux engine build
• first one which builds nativedebug as the debug info file is generated
• tests seem to be executed with Native Image - as it is missing Python
  • JavaScript related tests seems to run because of Remove JavaScript from bin/enso executable #12018
• second one seems to be using ENSO_JAVA=espresso

It would be better to split/restructure the CI jobs in the future, but as far as I can say, things seem to work as they used to. Good job.

[JaroslavTulach]

Also check line 283:

Espresso support works also with
[native image support](#engine-runner-configuration). Just make sure
`ENSO_JAVA=espresso` is specified when building the `runner` executable:

```bash
enso$ rm ./built-distribution/enso-engine-*/enso-*/bin/enso
enso$ ENSO_JAVA=espresso sbt --java-home /graalvm
sbt> engine-runner/buildNativeImage