fprime_test_api: Sometimes fprime_test_api does not connect to currently running fprime-gds session

[bevinduckett]

F´ Version	89a9e32 Bump werkzeug from 3.0.6 to 3.1.4 (#4480)
Affected Component	fprime gds integration library

---

Problem Description

Sometimes when pytest is run, fprime_test_api does not initialize correctly and terminates with an assert the first time it tries to send a command. When that happens, I usually immediately re-run pytest and it works the next time.

Context / Environment

Execute fprime-util version-check and share the output.

Operating System: Linux
CPU Architecture: x86_64
Platform: Linux-4.18.0-553.100.1.el8_10.x86_64-x86_64-with-glibc2.28
Python version: 3.9.25
CMake version: 3.26.0
Pip version: 26.0
Pip packages:
    fprime-tools==4.0.2a2
    fprime-gds==4.0.2a11.dev20+gad302b44e
    fprime-fpp==3.1.0a12
Project submodules:
    https://github.com/nasa/fpp.git @ v3.1.0a11-175-ge23d8412b
    https://github.com/nasa/fprime.git @ v4.0.1a1-103-g89a9e3247b
    https://github.com/fprime-community/fprime-baremetal @ b94a572
    https://github.com/fprime-community/fprime-vorago @ 91a7435

How to Reproduce

1. Start fprime-gds session
2. Write a simple test script
3. Run it multiple times using pytest (I haven't been tracking but it seems to happen less than 5% of the time)

Expected Behavior

If fprime-gds is running & there's no issues with the session, the test library should be able to connect 100% of the time.