unavailable `node.sock` error case is displaying misleading error

[plebhash]

@jayrmotta reported that when the Bitcoin Core node.sock is not available, the UI is displaying a misleading error

[plebhash]

one solution for this could come from the TS modules established on #82

ideally #82 should bootstrap TS code not only to display container logs on UI, but also to parse them so that the UI is able to display accurate information on different scenarios

---

on this specific scenario, whatever error logs come from JDC (see stratum-mining/sv2-apps#418) should help the UI inform the user about the fact that the provided Bitcoin Core node.sock is not available

[plebhash]

but also, when the user configures the Bitcoin Core node.sock for the first time (screenshot below), the TS code should make one initial validation to make sure that's available and prevent the user from going forward in case it's not

of course, after this initial validation, Bitcoin Core could still become unavailable later, so the log parsing described above should still be implemented

[plebhash]

with stratum-mining/sv2-apps#422 JDC logs on this error should become:

2026-04-09T00:41:01.708246Z  INFO jd_client_sv2: Job declarator client starting... setting up subsystems, User Identity: your_username_here
2026-04-09T00:41:01.708440Z  INFO jd_client_sv2: Initializing monitoring server on http://0.0.0.0:9091
2026-04-09T00:41:01.708841Z  INFO stratum_apps::monitoring::http_server: Starting monitoring server on http://0.0.0.0:9091
2026-04-09T00:41:01.708854Z  INFO stratum_apps::monitoring::http_server: Cache refresh interval: 15s
2026-04-09T00:41:01.708902Z  INFO jd_client_sv2: Using Bitcoin Core IPC socket at: /Users/plebhash/Library/Application Support/Bitcoin/node.sock
2026-04-09T00:41:01.709211Z  INFO jd_client_sv2: Attempting to initialize upstream...
2026-04-09T00:41:01.709216Z  INFO jd_client_sv2: Trying upstream 1 of 1: pool=75.119.150.111:3333, jds=75.119.150.111:3334
2026-04-09T00:41:01.709747Z  INFO bitcoin_core_sv2::template_distribution_protocol: Creating new BitcoinCoreSv2TDP via IPC over UNIX socket: /Users/plebhash/Library/Application Support/Bitcoin/node.sock
2026-04-09T00:41:01.709830Z ERROR jd_client_sv2::template_receiver::bitcoin_core: Failed to create BitcoinCoreToSv2: CannotConnectToUnixSocket("/Users/plebhash/Library/Application Support/Bitcoin/node.sock", "Connection refused (os error 61)")
2026-04-09T00:41:01.709940Z  INFO jd_client_sv2::channel_manager: Channel Manager: received shutdown signal
2026-04-09T00:41:01.709944Z  INFO jd_client_sv2: Shutdown requested while waiting to initialize upstream, aborting retries
2026-04-09T00:41:01.709958Z ERROR jd_client_sv2: Failed to initialize upstream: CouldNotInitiateSystem
2026-04-09T00:41:01.709989Z  WARN jd_client_sv2::channel_manager: Waiting for initial template and prevhash from Template Provider...
2026-04-09T00:41:01.709996Z  INFO jd_client_sv2::channel_manager: Channel Manager: received shutdown while waiting for templates
2026-04-09T00:41:01.709999Z  INFO jd_client_sv2: Spawning status listener task...
2026-04-09T00:41:01.710012Z  INFO jd_client_sv2: Waiting for BitcoinCoreSv2TDP dedicated thread to shutdown...
2026-04-09T00:41:01.710225Z  INFO jd_client_sv2: BitcoinCoreSv2TDP dedicated thread shutdown complete.
2026-04-09T00:41:01.710233Z  WARN jd_client_sv2: Graceful shutdown: waiting 5 seconds for tasks to finish
2026-04-09T00:41:01.710290Z  INFO stratum_apps::monitoring::http_server: Swagger UI available at http://0.0.0.0:9091/swagger-ui
2026-04-09T00:41:01.710296Z  INFO stratum_apps::monitoring::http_server: Prometheus metrics available at http://0.0.0.0:9091/metrics
2026-04-09T00:41:01.710327Z  INFO jd_client_sv2: Monitoring server: received shutdown signal.
2026-04-09T00:41:01.710340Z  INFO stratum_apps::monitoring::http_server: Monitoring server received shutdown signal, stopping...
2026-04-09T00:41:01.710424Z  INFO stratum_apps::monitoring::http_server: Monitoring server stopped
2026-04-09T00:41:01.710437Z  INFO jd_client_sv2: Monitoring server task exited and signaled fallback coordinator
2026-04-09T00:41:01.710446Z  INFO jd_client_sv2: All tasks joined cleanly
2026-04-09T00:41:01.710449Z  INFO jd_client_sv2: JD Client shutdown complete.
2026-04-09T00:41:01.710477Z  INFO jd_client_sv2: JobDeclaratorClient dropped

where the key line is:

2026-04-09T00:41:01.709830Z ERROR jd_client_sv2::template_receiver::bitcoin_core: Failed to create BitcoinCoreToSv2: CannotConnectToUnixSocket("/Users/plebhash/Library/Application Support/Bitcoin/node.sock", "Connection refused (os error 61)")

[lucasbalieiro]

I'm gonna start to tackle this one.
#90 is addressing only the setup process.

I'll get the part of the diagnostics and review #90