west debug: openocd: console garbled with --tui option

[erwango]

Describe the bug

gdb option --tui to split screen and display source along with gdb console is available as an openocd runner option.
Though, when used with west debug, it provides a garbled output:

When using --tui gdb arg outside of west debug, it works as expected

with following commands run in 2 different windows:

$ ~/zephyr-sdk-0.17.0/sysroots/x86_64-pokysdk-linux/usr/bin/openocd -s ~/zephyrproject/zephyr/boards/st/nucleo_l152re/support -s ~/zephyr-sdk-0.17.0/sysroots/x86_64-pokysdk-linux/usr/share/openocd/scripts -f ~/zephyrproject/zephyr/boards/st/nucleo_l152re/support/openocd.cfg -c 'tcl_port 6333' -c 'telnet_port 4444' -c 'gdb_port 3333' '-c init' '-c targets' '-c halt'

$ ~/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb-py -ex 'target extended-remote :3333' build/nucleo_l152re/zephyr/zephyr.elf -tui -ex load

To Reproduce
Steps to reproduce the behavior:

1. west build -b nucleo_f401re sample/hello_word
2. west debug -d build --tui
3. See error

Expected behavior
--tui should help debug experience, not garble it.

Impact
west debug not usable with --tui option

Logs and console output

Environment (please complete the following information):

• OS: (e.g. Linux, MacOS, Windows): Ubuntu
• Toolchain (e.g Zephyr SDK, ...): zephyr-sdk-0.17.0
• Commit SHA or Version used: v4.0.0.rc3

Additional context
I suspect a timing issue between gdb server and client command Doesn't seem to be the case.