Add CI job to validate NON-TEE launcher-based MPC deployment #1758

Background

follow up from #1735

With the introduction of NON-TEE launcher support, we now have a new supported deployment mode for MPC nodes that mirrors the TEE setup (docker-compose + launcher), but runs outside of a CVM.

While we already have CI coverage for:

building the MPC node image, and

validating that the MPC node container can initialize and start (TEE-oriented flow),

we currently do not have CI coverage that exercises the launcher itself in NON-TEE mode.

This means:

regressions in the launcher logic (platform handling, env propagation, sanitization, container startup) may go unnoticed,

the newly added NON-TEE path is not validated end-to-end in CI.

Proposed Change

Add a new CI job (separate from the existing TEE build job) that:

Builds (or pulls) an MPC node Docker image.

Runs the launcher Docker image in NONTEE mode using a docker-compose file.

Provides a test user_config file via bind-mount (as in non-TEE deployments).

Verifies that:

the launcher starts successfully,

the MPC container is launched by the launcher,

the MPC container remains running for a fixed period (e.g. 30–60 seconds).

Fails the job if:

the launcher exits unexpectedly,

the MPC container fails to start,

or the MPC container crashes shortly after startup.

This should be conceptually similar to the existing CI logic used to validate MPC node startup (e.g. docker run … sleep 60 … docker ps), but routed through the launcher instead of invoking the MPC image directly.

User Story

add an MPC developer I'd like to have CI check for the launcher /mpc builds

Acceptance Criteria

CI job is deployed

Resources & Additional Notes

No response