MultiZoomCoordinateSystemMapper Overwritten in Device:init

[amartya4256]

Describe the bug
In the current implementation, the Display seems to never use MultiZoomCoordinateSystemMapper for its coordinateSystemMapper. This mapper is used when rescalingAtRuntime is active but eventually Device:init is called at some point which overwrites the coordinateSystemMapper to a SingleZoomCoordinateSystemMapper. In case of a multi zoom setup, this makes the UI to behave weirdly when you drag and drop a tab across the screens.

To Reproduce

• Start the SDK product.
• Drag an editor tab to another monitor with a different DPI
• The Editor will not open where the preview is pointing to but rather a different location (slightly scaled)
  (My config was: Left monitor - primary - 175%, Right monitor - 100 %; Dragging from right to left)

Expected behavior
The top left corner of the dropped editor should be the same as where the cursor dropped it.

Environment:

1. Select the platform(s) on which the behavior is seen:

• • All OS
• • Windows
• • Linux
• • macOS

Introduced by #1630