Fix Copilot AWF startup path handling for Daily Issues Report failures

[Copilot]

The Daily Issues Report workflow was failing in scheduled runs with a generic “engine terminated before producing output” issue. The underlying failure was Copilot startup inside AWF chroot where node was not resolvable, causing early exit (127) before any agent output.

• Root cause addressed

  • Copilot AWF execution relied on node discovery that could be lost under chroot/sudo path behavior, resulting in a hard startup failure.

• Compiler/runtime command fix

  • Updated Copilot engine command generation to prepend the resolved GH_AW_NODE_BIN directory to PATH before launching AWF.
  • This preserves node resolution in AWF chroot and allows copilot_harness to start consistently.

• Golden fixture alignment

  • Updated affected wasm golden outputs for Copilot execution templates to reflect the new PATH line in generated workflow scripts.

GH_AW_NODE_BIN=$(command -v node 2>/dev/null || true)
export GH_AW_NODE_BIN
if [ -n "$GH_AW_NODE_BIN" ] && [ -x "$GH_AW_NODE_BIN" ]; then
  export PATH="$(dirname "$GH_AW_NODE_BIN"):$PATH"
fi