Microscope abstraction change to include SPM

[AustinHouston]

Now:
Microscope
| |
Thermo DigitalTwin

Future:
Microscope
| |
EM____ SPM______
| | | |
Real DT Real DT

Microscope.py turns into ElectronMicroscope.py

where

class ElectronMicroscope(Microscope)

and

class Microscope(Device)

***This will make server startup a mess, we could use yaml config files to keep track and init different servers for DT vs real

[AustinHouston]

Hmm i guess i don't know how to markdown properly

[Slautin]

@AustinHouston @gduscher @utkarshp1161
Do you think general methods like acquire_scanned_image() or acquire_spectrum() should be in the top Microscope class? They common for STEM and SPM, but if we later want to extend this to something like nanoindentation., or raman, or optics...
Maybe it is better to keep Microscope very general, with only things like Connect(), Disconnect(), etc.? What do you think?

The second thing. Where @abstract method should be define? If we create multilevel hierarchical structure and at each level (Instrument->Microscope->SPMMicroscope) we have @abstract methods it easy to get lost what you need to define in results

[AustinHouston]

good idea.
eventually, it could be:

Instrument (connect, etc)
|
Microscope (acquire_image, etc)
|
TypeofMicrosocpe (specific, aberration correction, eels, etc)

so this base should be called instrument. I think it's fine for now though

[Slautin]

Decided to have Instrument (very basic) -> SPM, STEM, Indenter ...

That should address the abstractmethod problem as well.

[utkarshp1161]

@Slautin, this change will be nice. I wont bias you with any comments now. Will add thoughts when you raise a PR.