feat(background-jobs): run background_job in Rex when its server is reachable
jobs launched from pi died with the pi session, and their output was only visible through the tool. when `rex whoami` answers, background_job now starts the command as a labeled Rex terminal ($REX_SESSION inside Rex, otherwise a pi-<project> session) and makes `rex wait --json BLOCK` the task's child process. completion still wakes the agent once, with the pane's screen from `rex capture --unwrap` as the output tail. stop captures the pane and closes it. session shutdown only kills the waiters, so jobs keep running in Rex after reload, fork, or pi exiting. monitors stay local: Rex emits no per-line output events. PI_BACKGROUND_JOBS_REX=0 opts out. verified against a live Rex server: exit codes and stderr propagate, 300-line output survives capture, and a job started by `pi -p` finished after pi exited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>