#9018: Dashboard - Zoom in/out on maps connected to a 3D map

[mahmoudadel54]

Description

This PR includes fixing the inconsistently issue of zoom in/out that happens in 3d map sync with another map [2d or 3d].
The issue in 3D maps was that dependenciesToMapProp.js file updates center and zoom for map object into widgets state for the synced maps, and due that update _updateMapPositionFromNewProps method into Map.js of cesium is called to update the map view.
The issue was in these lines:

MapStore2/web/client/components/map/cesium/Map.jsx

Lines 504 to 511 in 2d097ff

	const position = {
	destination: Cesium.Cartesian3.fromDegrees(
	newProps.viewerOptions?.cameraPosition?.longitude ?? newProps.center.x,
	newProps.viewerOptions?.cameraPosition?.latitude ?? newProps.center.y,
	newProps.viewerOptions?.cameraPosition?.height ?? this.getHeightFromZoom(newProps.zoom ?? 0)
	),
	orientation: newProps.viewerOptions?.orientation
	};

It does not take the new props of center that was updated within dependenciesToMapProp as mentioned above.

I have added 2 enhancements:

• absolute the substitute value here:

  MapStore2/web/client/components/map/cesium/Map.jsx

  Line 489 in 2d097ff

  return a.toFixed(12) - b.toFixed(12) <= 0.000000000001;

  
  as during test I tried to move from a point with negative coordinates to a point with positive coordinates and vice versa so if the result with negative value, the logic of isNearlyEqual will not be accurate as expected.
• adding round to zoom values as in some cases the calculated zoom level from height adds a very small tolerance to the zoom level like: zoom = 6, the calculated zoom level = 6.0000008 which will update the view unnecessarily and actually this was my first try to fix the issue mentioned into the demo issue.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Issue

#9018

What is the current behavior?
#9018

What is the new behavior?
Now the zoom restriction that seems in the issue is fixed

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[allyoucanmap]

@mahmoudadel54 @tdipisa I did a local test with this implementation and there are still problems with the zoom, see video below:

dashboard-zoom.mp4

I've also investigated on the reason of this behaviour and I noticed that the camera event moveEnd it's triggered twice everytime a view has been changed on 3D map, unfortunately I was not able to find the reason of this and I think additional time is needed to understand the problem and find a proper solution.
For the moment we could keep the hardening done on center and zoom.

[allyoucanmap]

Please restore this to the previous arguments, if we want to propertly control the camera direction we will need to include the viewerOptions property to the widgets dependecies.

[allyoucanmap]

forgot to add request changes
see #10460 (review)

[tdipisa]

@mahmoudadel54 let's keep this on hold for a moment. Wait for my feedback, please. Thank you @allyoucanmap.