[CI] quick fix for SATIE test suite

This MR comments out server.remove at the end of our unit test tearDown functions. This quick and dirty fix will keep the CI form failing randomly. We will see server name already exists warnings, but they can be ignored.

Basically, calling server.remove immediately after satie.quit sometimes causes problems. Quitting SATIE is an async operation, and removing the server can leaving things in an awkward state.

This MR now tries extending wait times to 20 seconds to see if this solves the issue temporarily.

We need to find a proper solution, but in the mean time this keeps the CI working.

Closing as neither of the changes tried here truly made any difference.