Investigate the signal messages arising after the C++ tests pass

[anutosh491]

Though #627 implements a debugger client and enables the C++ tests for the debugger again, we encounter some Error : signal 11 issues after the tests pass

registering handler for SIGSEGV
PYTHONHOME not set or not initialized.
Core instantiated
Starting xeus-python kernel...

If you want to connect to this kernel from an other client, you can use the kernel-debug.json file.
Run with XEUS 5.1.1
XDEBUGGER: the debugger has started
XDEBUGGER: the debugger has stopped
Error: signal 11:
0   xpython                             0x0000000[10](https://github.com/jupyter-xeus/xeus-python/actions/runs/9810163222/job/27089703661#step:10:11)a33b99e _ZN4xpyt15sigsegv_handlerEi + 46
1   libsystem_platform.dylib            0x00007ff816131dfd _sigtramp + 29
2   ???                                 0x0000000000000004 0x0 + 4
3   libpython3.12.dylib                 0x000000010ac59c92 subtype_dealloc + 1202
4   libpython3.12.dylib                 0x000000010ac59c92 subtype_dealloc + 1202
5   libpython3.12.dylib                 0x000000010ac59ce1 subtype_dealloc + 1281
6   libpython3.12.dylib                 0x000000010ac59c92 subtype_dealloc + 1202
7   xpython                             0x000000010a2e4b10 _ZN4xpyt8debuggerD2Ev + 80
8   xpython                             0x000000010a2e4b8e _ZN4xpyt8debuggerD0Ev + 14
9   libxeus.11.1.1.dylib                0x000000010a5e4cb1 _ZN4xeus7xkernelD2Ev + 97

As can be seen after the debugger has stopped we encounter a signal issue out of xkernel's destructor. This should be looked into.