Bump score_lifecycle pin and fix simple_lifecycle mw::com config

[hskang-amelia]

What

Two changes, verified together against a real launch_manager run:

1. Bump score_lifecycle from 85da2168328d17a3cf53791ebf93534e5ed921fc
   to 9b86164ac1f850f76ac8ce743be903f98a60f422 (current main), and migrate
   showcases/simple_lifecycle/configs/launch_manager_config.json to the
   _ms field names/units that Use milliseconds directly in launch manager config schema lifecycle#637 introduced
   (already merged upstream; this repo's pin just hadn't caught up).

2. Package mw_com_config.json for the simple_lifecycle showcase.
   launch_manager and its supervised components (control_daemon,
   cpp_supervised_app, rust_supervised_app) all initialize mw::com's
   LmControlService (ActivateRunTarget/GetActiveRunTarget), which needs
   a mw_com_config.json. showcases/simple_lifecycle/BUILD never packaged
   one — unlike showcases/standalone/BUILD, which does — so on a real run
   launch_manager itself aborted immediately, and after fixing that,
   every supervised component still failed the same way and sat in
   launch_manager's fallback restart loop, since ProcessGroupManager
chdirs each component into bin_dir before exec'ing it — a different
   directory than launch_manager's own cwd.

Why

Found while independently verifying eclipse-score/lifecycle#654 end-to-end
against this repo's simple_lifecycle showcase (the only place in this repo
that exercises launch_manager's real ControlProvider alongside a real
mw::com client). Neither issue is specific to #654 — both are pre-existing
gaps that just hadn't been exercised, since simple_lifecycle wasn't
runnable end-to-end before this.

How

• mw_com_config.json is the same LmControlService service definition
  already used by lifecycle's own integration tests (service id 7101,
  methods ActivateRunTarget/GetActiveRunTarget).
• It's staged at both data/simple_lifecycle/etc/ (via the existing
  custom_layout, for launch_manager's own cwd) and bin/etc/ (via a
  small extra pkg_files target passed through other_package_files, for
  each component's cwd) — score_pkg_bundle's custom_layout can only
  place files under data/NAME/, so it can't reach bin/etc/ on its own.

Testing

Built and ran the bundle end-to-end in
ghcr.io/eclipse-score/devcontainer:v1.11.0 (this sandbox's host glibc is
too old for the Bazel-pulled Rust toolchain the bumped module needs):

bazel build --config=linux-x86_64 //showcases/simple_lifecycle:simple_lifecycle

Extracted and ran the resulting bundle directly: launch_manager starts
cleanly, supervises control_daemon/cpp_supervised_app/rust_supervised_app
with no mw::com initialization errors, correctly transitions to the fallback
run target when cpp_supervised_app's SIGUSR1 simulates a fault, and shuts
down with exit code 0 on SIGTERM. Before this change, launch_manager
aborted on startup (missing config) and, once that was worked around,
control_daemon crash-looped every ~150ms indefinitely.

🤖 Generated with Claude Code

[github-actions]

The created documentation from the pull request is available at: docu-html