Describe the bug
Getting some error message "Failed request assertion is not found" when probing.

To Reproduce
Steps to reproduce the behavior:

1. Use the following config.yaml

probes:
  - id: 'http-1'
    name: 'mock-test'
    requests:
      - url: http://0.0.0.0:7001/v1/hello
    alerts:
      - assertion: response.status < 200 or response.status > 308
        message: HTTP Status is not 200
      - assertion: response.ime > 2000
        message: Too sloow

2. Start probing using: npm start -- -c config.yaml
3. Start your local mock server
4. Then disable/turn off the mock server

Expected behavior

1. Assertion exist, should have no problem finding it even when connection is refused

Screenshots

Desktop (please complete the following information):

• OS: WIndows 11 and WSL (Ubuntu 24.04 LTS)
• Lateest monika from main branch

Additional context
Seems to appear when disconnected/ERCONNREFUSED error