Move espresso NI build to a separate CI job

[Akirathan]

Engine Checks GH action currently builds 3 native images:

• engine-runner (for example at https://github.com/enso-org/enso/actions/runs/14469147478/job/40578473562#step:10:2325)
• ydoc
• engine-runner with espresso (for example at https://github.com/enso-org/enso/actions/runs/14469147478/job/40578473562#step:10:4991)

engine-runner NI with espresso is build via env ENSO_JAVA=espresso sbt engine-runner/buildNativeImage (for example in https://github.com/enso-org/enso/actions/runs/14469147478/job/40578473562#step:10:4991) and there are no sanity checks for it, only NI is build.
This step is defined in

enso/build_tools/build/src/engine/context.rs

Line 452 in 9ac30c2

.arg("engine-runner/buildNativeImage")

and the sanity checks should be run, but are not.

Optimally, move the build of engine-runner with espresso and its sanity checks to a separate CI job.

Tasks

• Ensure sanity checks run for engine-runner with espresso
• Move NI build of engine-runner with espresso to a different job

[JaroslavTulach]

• Enso will probably never use Espresso for production
• make build faster and simpler is a priority
• let's remove support for Espresso altogether for now