[roll] Roll fuchsia [ffx][isolate] Make daemon startup explicit and non-daemonized

Daemon autostart will daemonize the started daemon via a double fork.
This makes ffx daemons live as long as the surrounding session, aka the
entire test. When the test's process group receives a signal it'll
also goes to spawned daemons.

In general we should not test daemon autostart in an e2e flow UNLESS we
specifically handle killing daemons spawned by isolates.

Locally, Ctrl-C sends SIGHUP to all processes within the group which now
includes running daemons.

In Infra, they can switch to using `kill -<signal> -<pid>`
(note the `-`) to kill all processes spawned in the test's process
group.

On abnormal termination tests still leave daemons behind. Depending on
the type of session management employed by your environment these
daemons will either receive SIGHUP from the session manager/`init` or
not.

This removes the isolate cleanup code as zombified daemons are no longer
automatically cleaned up by the surrounding session manager. This makes
them unkillable, which means self-test hangs. It also turned out to be
painful to associate the daemon with the isolate as some tests may want
to kill the daemon themselves.

Fixes: 127012
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/858516
Original-Revision: 56612925ff260fc8e9329ad12a8bfa57a43867cf
GitOrigin-RevId: 8f15fd63110bb405a463ca696225fc18e15ce9da
Change-Id: Iee369c63e917cf71d473fcf786751df5e3a7db88