[BUG] Improve message to avoid raising alarms when ssh timeouts initially

### Affected Command

ewc hub deploy [ITEM]

### Describe the issue

When deploying Items, the cli seems to try to execute `ansible` as soon as the VM provisioning call returns. However, this may lead to `ansible` failing prematurely due to the `sshd` service not being ready to accept requests. Although the cli retries right away and even manages to complete, the error message that is logged during the attempts seems alarming and might confuse users or hinder trust on the success of the operation.

### Steps to Reproduce

1. Run `ewc hub deploy ssh-bastion-flavour`

### Expected Behavior

The cli silently deals with newly provisioned VM cold start, waiting until `sshd` starts taking in traffic before attempting to execution `ansible`, and raises an error only when a business-defined ssh connection timeout is reached.

### Logs or Output

```shell
TASK [Gathering Facts] ******
[02/02/26 11:39:15] ERROR ❌ Task 'ansible-playbook -i'

...

fatal [192.168.1.82]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to host via ssh: ssh: connect to host 192.168.1.82 port 22: Connection timed out", "unreable": true}

...

[02/02/26 11:39:15] WARNING Attempt 1/5 failed
[02/02/26 11:39:15] INFO Retrying in 10 seconds
```

### Environment

Linux

### EWC CLI Version

0.2.1