API launches before Jupyter is up causing API to fail to connect to jupyter for some time.

**Description:**
The system fails to check if Jupyter is running, resulting in repeated connection errors.

**Steps to Reproduce:**
1. Start the application using the following command:
```
docker run -d \
-p 3000:3000 \
-p 8080:8080 \
-v briefer_psql_data:/var/lib/postgresql/data \
-v briefer_jupyter_data:/home/jupyteruser \
-v briefer_briefer_data:/home/briefer \
briefercloud/briefer
```
3. Wait for the server to initialize.
4. Observe logs indicating failure to connect to Jupyter.

**Note:** have jupyter running on http://localhost:8888

**Expected Behavior:**
The application should successfully verify if Jupyter is running without connection issues.

**Actual Behavior:**
The following error message appears repeatedly in the logs:
```
Failed to check if Jupyter is running
err: {
"type": "TypeError",
"message": "fetch failed: connect ECONNREFUSED ::1:8888",
"stack":
TypeError: fetch failed
at node:internal/deps/undici/undici:12618:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
caused by: Error: connect ECONNREFUSED ::1:8888
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
}
```

The payload names no source files or tests. Reproduce the Docker startup command and trace the API's Jupyter health check during initialization; done when the application handles Jupyter starting later without repeated connection failures and connects successfully once Jupyter is available.

Written by the indexing model from the issue text.