Avoid SIGHUP error message in connectivity server log file

[bieryAtFnal]

Description

We have noticed occasional error messages like the following in regression test logfiles:

pytest-9439/run4/log_biery_lr-session_local-connection-server.txt:[2025-11-04 10:59:16 -0600] [3574082] [ERROR] Worker (pid:3574083) was sent SIGHUP!

Primarily these messages appear in the connectivity server log file, but occasionally they appear in the root controller log file.

Claudia provided a fix for the connectivity server occurrences of the problem in DUNE-DAQ/daqsystemtest#259. That fix slightly changes the commands that we use to start up and shut down the connectivity server.

This PR in the listrev repo copies those changes to the ConnSrvr startup/shutdown to the listrev_test.

To these these changes, one would simply run the listrev_test.py and confirm that it completes without any complaints.

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature or enhancement (non-breaking change which adds functionality)
• Optimization (non-breaking change that improves code/performance)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Testing checklist

• Unit tests pass (e.g. dbt-build --unittest)
• Minimal system quicktest passes (pytest -s minimal_system_quick_test.py)
• Full set of integration tests pass (daqsystemtest_integtest_bundle.sh)
• Python tests pass if applicable (e.g. python -m pytest)
• Pre-commit hooks run successfully if applicable (e.g. pre-commit run --all-files)

Further checks

• Code is commented where needed, particularly in hard-to-understand areas
• Code style is correct (dbt-build --lint, and/or see https://dune-daq-sw.readthedocs.io/en/latest/packages/styleguide/)
• If applicable, new tests have been added or an issue has been opened to tackle that in the future.

[wanyunSu]

LGTM