Flakey test: jbpf_io_ipc_test

The jbpf_io_ipc_test fails at Ubuntu22.04:

Experimental Features, Static
staticBuildParam: -e JBPF_STATIC=1 -e JBPF_EXPERIMENTAL_FEATURES=1
sanitizerBuildParam:

https://belgrade.visualstudio.com/jbpf/_build/results?buildId=21487&view=logs&j=5da2191b-af8a-520c-3df0-5801c3516851&t=1bc62390-0a51-53db-b3c0-3bf9190da06b

 73/116 Test  #73: io/jbpf_io_ipc_test ................................................***Exception: SegFault  1.41 sec
2025-03-13T16:40:58.547514Z [JBPF][IO][INFO]: Directory '/tmp/jbpf' already exists.
2025-03-13T16:40:58.549854Z [JBPF][IO][INFO]: Registered thread id 0
2025-03-13T16:40:58.550108Z [JBPF][MEM_MGMT][INFO]: Trying 2MB persistent huge pages (0 bytes)
2025-03-13T16:40:58.550145Z [JBPF][MEM_MGMT][INFO]: No huge page allocation
2025-03-13T16:40:58.550154Z [JBPF][MEM_MGMT][WARN]: Could not allocate memory
2025-03-13T16:40:58.550159Z [JBPF][MEM_MGMT][INFO]: Trying 2MB transparent huge pages (0 bytes)
2025-03-13T16:40:58.550167Z [JBPF][MEM_MGMT][WARN]: Could not allocate memory
2025-03-13T16:40:58.550172Z [JBPF][MEM_MGMT][INFO]: Let's try to allocate regular memory
2025-03-13T16:40:58.550177Z [JBPF][MEM_MGMT][INFO]: No huge page allocation
2025-03-13T16:40:58.570457Z [JBPF][MEM_MGMT][INFO]: Memory allocated successfully at address 0x7fb198040000
2025-03-13T16:40:58.575776Z [JBPF][MEM_MGMT][INFO]: Allocated pages mlocked in memory
2025-03-13T16:40:58.581452Z [JBPF][MEM_MGMT][DEBUG]: Successfully created memory arena of size 33554432 at address 0x7fb198040000
2025-03-13T16:40:58.581587Z [JBPF][IO][DEBUG]: Primary initialization successful
2025-03-13T16:40:58.581612Z [JBPF][IO][INFO]: Registered thread id 1
2025-03-13T16:40:58.581877Z [JBPF][IO][INFO]: Registered thread id 2
2025-03-13T16:40:58.581985Z [JBPF][IO][INFO]: Directory '/tmp/jbpf' already exists.
2025-03-13T16:40:58.585681Z [JBPF][IO][INFO]: Process connected. Initiating registration
2025-03-13T16:40:58.585700Z [JBPF][IO][INFO]: Received new incoming connection from control channel
2025-03-13T16:40:58.586293Z [JBPF][IO][INFO]: Sent registration request
2025-03-13T16:40:58.587097Z [JBPF][IO][INFO]: Registered new peer with socket fd 6
2025-03-13T16:40:58.587229Z [JBPF][MEM_MGMT][INFO]: Trying 1GB persistent huge pages (1073741824 bytes)
2025-03-13T16:40:58.587239Z [JBPF][MEM_MGMT][INFO]: No huge page allocation
2025-03-13T16:40:58.587242Z [JBPF][MEM_MGMT][INFO]: Openning shared memory with name jbpf_io_6
2025-03-13T16:40:58.587275Z [JBPF][MEM_MGMT][INFO]: Directory '/tmp/jbpf' already exists.
2025-03-13T16:40:58.587365Z [JBPF][MEM_MGMT][INFO]: Memory allocated successfully at address 0x7fb14c000000
2025-03-13T16:40:59.219363Z [JBPF][MEM_MGMT][INFO]: Allocated pages mlocked in memory
2025-03-13T16:40:59.459125Z [JBPF][IO][INFO]: Initiating negotiation with address 0x7fb14c000000
2025-03-13T16:40:59.459156Z [JBPF][IO][INFO]: Added context for sock_fd 6
2025-03-13T16:40:59.459738Z [JBPF][IO][INFO]: Got a local request
2025-03-13T16:40:59.459750Z [JBPF][IO][INFO]: Creating channel f5ffffffffffffffffffffffffffffff
2025-03-13T16:40:59.459804Z [JBPF][IO][INFO]: Received registration response with status 2
2025-03-13T16:40:59.459835Z [JBPF][IO][INFO]: Trying to mmap memory in address 0x7fb14c000000
2025-03-13T16:40:59.459841Z [JBPF][MEM_MGMT][INFO]: Will try to read file /tmp/jbpf/jbpf_io_6
2025-03-13T16:40:59.459974Z [JBPF][IO][INFO]: Memory mapping succeeded
2025-03-13T16:40:59.459986Z [JBPF][IO][INFO]: Sending notification
2025-03-13T16:40:59.829401Z [JBPF][IO][ERROR]: Error registering IPC in jbpf_io_ipc_register
jbpf_io_ipc_test: /jbpf/jbpf_tests/functional/io/jbpf_io_ipc_test.c:300: run_secondary: Assertion `io_ctx' failed.

Another instance:
https://belgrade.visualstudio.com/jbpf/_build/results?buildId=21496&view=logs&j=b59d232b-0f87-5f92-3949-4e26e78aed03&t=5c90e648-9c26-53d8-96cd-92cf667e4b94

Start by reproducing io/jbpf_io_ipc_test on Ubuntu 22.04 and reviewing the failure around jbpf_tests/functional/io/jbpf_io_ipc_test.c:300 in run_secondary. Use the provided build logs to investigate the jbpf_io_ipc_register error and preceding shared-memory or IPC events. Done means the test no longer intermittently segfaults or fails its io_ctx assertion.