Handle the failure cases of the profiler-cli daemon creation and communication gracefully #6230

Currently when the cli runs on a sandboxed environment that it doesn't have access to unix sockets or the PROFILER_CLI_SESSION_DIR directory, we show an error like this without much info:

Error: Daemon process exited unexpectedly during startup (exit code 0). Run with PROFILER_CLI_SESSION_DIR set and check the session directory for a log file, or re-run after upgrading Node.js.

Let's improve these failure cases properly and show more useful errors to the user.

┆Issue is synchronized with this Jira Task