Ignore flaky test failing on spurious OpenSSL errors

This test has been introduced by #3024
but is flaky because a similar OpenSSL error occurs but for an unrelated reason.

It the original ticket, the issue was clients failing to disconnect
properly after a successful session. In the flaky case, the client is
not even able to establish an MQTT connection:

```
Jan 27 13:06:41 0578accd2d08 mosquitto[787]: 1737983201: New connection from 127.0.0.1:35138 on port 8883.
Jan 27 13:06:41 0578accd2d08 mosquitto[787]: 1737983201: OpenSSL Error[0]: error:0A000126:SSL routines::unexpected eof while reading
Jan 27 13:06:41 0578accd2d08 mosquitto[787]: 1737983201: Client <unknown> disconnected: Protocol error.
```

To be compared to a client that connects successfully:

```
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194: New connection from 127.0.0.1:55188 on port 8883.
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194: New client connected from 127.0.0.1:55188 as suftwjdgsw (p2, c1, k60).
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194: No will message specified.
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194: Sending CONNACK to suftwjdgsw (0, 0)
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194: Received SUBSCRIBE from suftwjdgsw
Jan 28 08:49:54 1bc252b47d05 mosquitto[1305]: 1738054194:         c8y/s/dat (QoS 1)
```

Signed-off-by: Didier Wenzek <[email protected]>

Author: didier-wenzek

tests/RobotFramework/tests/tedge_connect/tedge_connect_test.robot

@@ -64,6 +64,8 @@ tedge reconnect restarts mapper
     Should Not Be Equal    ${pid_before}    ${pid_after}
 
 Check absence of OpenSSL Error messages #3024
+    Skip
+    ...    msg=This test is flaky. There is client (yet to be identified) that fails to connect on port 8883 leading to OpenSSL Error
     ${SuiteStart}=    Get Suite Start Time
     # Only checkout output if mosquitto is being used
     ${output}=    Execute Command