fix(cua-driver): report daemon_running accurately from socket liveness (#4019)

* fix(driver): report daemon_running accurately from socket liveness (#3981)

permissions status was reporting daemon_running: false whenever direct permissions were pending or unreadable, even when the daemon socket was actively listening. This also caused CLI remediation to erroneously suggest starting the daemon when it was already running.

This updates run_permissions_status to evaluate socket liveness via is_daemon_listening and propagate it accurately in both JSON and human-readable outputs.

* fix(cua-driver): simplify permission status output and cover socket liveness

Mutate the owned successful response without cloning it. Exercise the CLI against isolated Unix sockets for offline, pending, rejected-attribution, and trusted replies in JSON and text output.

Co-authored-by: injaneity <44902825+injaneity@users.noreply.github.com>

* test(cua-driver): remove oversized permission status test fixture

Keep the maintainer follow-up scoped to the owned-response simplification and formatting. Existing focused protocol checks remain unchanged.

Co-authored-by: injaneity <44902825+injaneity@users.noreply.github.com>

* fix(cua-driver): share unknown permission status messages

Choose the explanation and remediation once for JSON and text. Leave successful permission responses unchanged to keep the fix scoped to unknown-status liveness.

Co-authored-by: injaneity <44902825+injaneity@users.noreply.github.com>

* fix(cua-driver): use one unknown permission status message

Select one complete message by liveness and reuse it in JSON and text output.

Co-authored-by: injaneity <44902825+injaneity@users.noreply.github.com>

---------

Co-authored-by: shobhitagnihotri69 <shobhitagnihotri69@users.noreply.github.com>
Co-authored-by: injaneity <44902825+injaneity@users.noreply.github.com>