test(integration): refresh container-cjs_node24 log snapshot

The container-cjs_node24 snapshot was originally captured during a
container init that timed out and recovered. That left two artifacts
that no other container snapshot shares:

  - a leading `INIT_REPORT ... Status: timeout` line
  - the cold-start `END Duration` line missing the `(init: XXXX ms)`
    segment that AWS Lambda normally bundles when init completes
    inside the budget

After routing integration tests to dind runners (faster image cache)
and shipping handler.mjs as the sole entrypoint (no shim probing), the
container init now reliably finishes inside the init budget. The new
log shape matches every sibling container snapshot
(container-cjs_node18/20/22 and container-esm_node18/20/22/24).

Refresh the snapshot to that shape. After this change,
container-cjs_node24.log is byte-aligned with container-cjs_node22.log
on the `END Duration` line positions (107, 213, 319, ...).

Author: zarirhamza

integration_tests/snapshots/logs/container-cjs_node24.log

@@ -1,4 +1,3 @@
-INIT_REPORT Init Duration: XXXX ms	Phase: init	Status: timeout
 START
 {
   "e": XXXX,
@@ -105,7 +104,7 @@ START
     ]
   ]
 }
-END Duration: XXXX ms Memory Used: XXXX MB
+END Duration: XXXX ms (init: XXXX ms) Memory Used: XXXX MB
 START
 {
   "e": XXXX,