All Instruments: Expand the post install tests so that they give us more confidence that the server is correctly deployed

As a system developer and tester I would like to be able confirm that changes to an instrument system, for example a change to Windows 10 (see #5489), or software install or hardware update, have left the system in a _demonstrably_ working state.

Some IOC test framework and System tests in particular (run in groups or individually) could go a long way to establishing that no regression in overall system functionality has occurred, regardless of the system change. This could be used optionally to test the validity of a IBEX deployment - but the main goal is the wider system (hardware, platform, network, software, including IBEX).

***Acceptance Criteria***
- [ ] Initially, a useful subset of IOC or system tests can be run on the target system, individually or grouped (more tests should be easily be added/converted easily once this ticket has been done)
- [ ] The tests chosen are appropriate to "proving/qualifying" the new system so should ideally challenge the system.
- [ ] Tests included take account of comments in the notes below.
- [ ] The use of these tests on a live system in a diagnostic capacity should be considered.

***Notes***
1. It might be most useful to consider starting with the system to test "as-is" rather than always generating extra test artefacts (new clean folders etc).
2. The systems (on VHDs) could be snapshotted first, tested and then restored to a previous state to guarantee to clean up tests safely - this could also remove some need for some test clean-up code. It is important that any modifications for testing can be _completely_ removed from a _live_ instrument under test.
3. Hardware "in the loop" could and should be tested where possible so the ability to switch off simulation and drive hardware safely but diagnostically on a test or IOC basis will greatly expand the value of the testing.

Inizia individuando il framework di test IOC esistente e i test di sistema citati nell’issue, quindi esamina come i test vengono raggruppati o eseguiti singolarmente. Individua un piccolo sottoinsieme idoneo che possa essere eseguito su una destinazione così com’è ed esamina le note su snapshot, pulizia, sistemi live e test hardware-in-the-loop. Il lavoro è concluso quando il sottoinsieme può essere eseguito singolarmente o come gruppo e può essere utilizzato in sicurezza per valutare un deployment.

Scritto dal modello di indicizzazione a partire dal testo della issue.