feat(widgets): Remove onViewportChange Update Guard for Widgets

[chrisgervang]

For #9278

Background

This PR addresses an issue in onViewportChange where an optimization can prevent widgets from receiving a viewport. The issue was first noticed in the react environment because lastViewports is set before all widgets are fully mounted, leaving some widgets in an uninitialized state.

To resolve this, the guard logic in onViewportChange has been removed and the responsibility for handling performance concerns, such as avoiding excessive calls to onViewportChange, is pushed to individual widgets.

Change List

• Removed guard conditions in onViewportChange that previously compared lastViewports.
• Prevent excessive updates to the Compass widget when viewports change.

Alternative Considered

Widget Manager Updates Viewports: Fully delegate viewport updates to the widget manager by comparing state directly on the widget instead of relying on lastViewports.

• Drawbacks: Assumes all widgets store viewports in a consistent format, introducing unwanted rigidity.
• lastViewports would still remain, as it is used by the manager for other purposes.

This approach was ultimately not chosen to avoid adding required elements to the Widget interface.

[coveralls]

coverage: 91.701% (-0.006%) from 91.707%
when pulling ea1f7b4 on chr/remove-widget-manager-optimization
into 05bca74 on master.