CI fails when other jobs are running because of time out.

[n-eiling]

See https://git.rwth-aachen.de/acs/public/villas/node/-/jobs/5510111 for details.

Relevant output:

[TIME]  pipe-loopback-zeromq (ran for more then 1m)
[SKIP]  pipe-python-protobuf: Test is broken
[SKIP]  relay: Test is broken
[PASS]  signal (ran for .100993659s)
[PASS]  test-config (ran for 7.858488891s)
Summary: 1 of 61 tests failed.
   Timedout: 1
   Skipped: 18

Maybe we can remove the time out?

[stv0g]

I guess the timeout is probably more of an indicator for a broken test?

Shouldn't we attempt to fix the test, or disable it?

[n-eiling]

The test does work if it I rerun it. So it seems to work, but is just too slow if run in parallel with everything else.
I haven't investigated thoroughly though and I don't know if a similar functionality is tested in another test.