Automatic Client/Server Smoke Test in CI

Has this feature been discussed and generally agreed?

@pljones and @ann0see raised the idea to run automatic client/server smoke tests in CI (#2423). I second this idea.
At least with Ubuntu/Debian this should be very doable.

Describe the solution you'd like

• Start a Docker container, install jamulus-headless, start it as server
• Start another Docker container, install jamulus-headless, start it as headless client
• Verify that the client connected properly (#1975 might help)
• Exit.
• Repeat for all supported Ubuntu/Debian releases

It's probably sufficient to run this on all (pre-)releases, but not on every push or PR. It would be nice to have that for all platforms, but let's start with the simple stuff. This would already confirm that packaging works and basic Jamulus functionality is there without crashing right away.

Testing for compatibility (old server + new client, old client + new server) would also be interesting.

Describe alternatives that have been considered

Rely on manual testing and see it break as we don't cover all platforms... :)

Inizia leggendo la proposta in #2423 e il contesto della verifica della connessione in #1975, quindi esamina la configurazione esistente di Docker, packaging e CI del repository. Definisci un job CI che avvii container server e client di jamulus-headless per le release di Ubuntu/Debian supportate e verifichi la connessione del client prima di terminare. Il lavoro è completato quando lo smoke test viene eseguito secondo la pianificazione delle release scelta e fallisce se il packaging o l'avvio di base di client/server non funziona.