List of microscopes

Encode the list of microscope as a hardcode in smartem_backend initially, to be updated by hand, then look at better ways of doing it. This may be useful for authenticating smartem_agents (do we recognise this microscope) and potentially for `/admin` route in the f/e

This is the list:

- Krios 1 - m02
- Krios 2 - m03
- Talos - m04
- Scios - m05
- Krios 3 - m06
- Krios 4 - m07
- Krios 5 - m08
- Glacios 1 - m10
- Aquilos - m11
- Glacios 2 - m12
- Leica cryoCLEM - m14

the true source of truth is UAS which we don’t have programmatic access to. it’s the user administration system. it’s how users apply for beam time and see what is scheduled. [uas.diamond.ac.uk](http://uas.diamond.ac.uk/). it’s separated from other systems so a bunch of the information in there ends up being mirrored in ISPyB (https://github.com/DiamondLightSource/ispyb-database) which is what we use as the source of truth for sessions and what instrument they’re booked on. Guilherme de Freitas may have ideas on how to get this list programatically.

Inizia individuando smartem_backend e i suoi punti di ingresso esistenti relativi all’autenticazione o ai microscopi, quindi esamina come il frontend /admin e smartem_agents potrebbero utilizzare l’elenco. Conferma le corrispondenze microscopio-id indicate nell’issue e rendi l’elenco disponibile per il riconoscimento e l’uso amministrativo; documenta qualsiasi limitazione rimanente relativa alla fonte di verità che coinvolga UAS o ISPyB.

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