Adding DetuningMap, DMM

[a-corni]

In this draft, I have tried to define a DetuningMap, a DMM and the way to define them via Register, Register3D, MappableRegister, RegisterLayout for the DetuningMap, and in Device for the DMM.
I think the easiest way to draw a DetuningMap is via RegDrawer. The fact that I defined DetuningMap in the module dmm, separately from RegDrawer and Register creates a circular import: To define a Register you need a DetuningMap that needs a RegDrawer that needs the register module to finish intializing.
Conclusion: with the current draft, the next step would be to move the DetuningMap to the register module, and -I guess- DMM to the channel module.

[HGSilveri]

I refactored as you suggested. I also made DetuningMap and subclass of WeightMap and made some changes to fix broken UTs.
Since this changes BaseDevice, we will need to update the JSON schema accordingly...

[a-corni]

Here is the rendering of a DetuningMap built from a RegisterLayout:

layout = RegisterLayout([[0, 0], [1, 0], [0, 1], [1, 1]])
det_map_1 = layout.define_detuning_map({0:0.09, 1:0.8, 2:0.11, 3:0})

The rendering is the same for :

layout = RegisterLayout([[0, 0], [1, 0], [0, 1], [1, 1]])
det_map_1 = layout.define_detuning_map({0:0.089, 1:0.8, 2:0.111, 3:0})

If the detuning map represents the one of a SLM Mask (all weights are the same), the representation is the same as before:

Here is the representation when two points are too close:

layout = RegisterLayout([[0, 0], [1, 0], [0, 1e-2], [1, 1]])
det_map_1 = layout.define_detuning_map({0:0.8, 1:0.0, 2:0.2, 3:0})

[HGSilveri]

I realized that we don't need the DMMs to be added to the pre-defined devices yet and it actually causes issues, so I just removed it from IroiseMVP and added some TODOs instead.

[a-corni]

Perfeito !