Do not reset zoom when switching between workspaces

[klakhov]

Motivation and context

An improvement requested by the data annotation team: switching between workspaces (standard and review) caused the zoom level to reset, which was not user-friendly. This PR addresses the issue.

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see GitHub docs)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 85.71429% with 1 line in your changes missing coverage. Please review.

Project coverage is 74.17%. Comparing base (21db1d4) to head (dfaff4e).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #9233   +/-   ##
========================================
  Coverage    74.16%   74.17%           
========================================
  Files          428      428           
  Lines        44964    44971    +7     
  Branches      3918     3919    +1     
========================================
+ Hits         33348    33356    +8     
+ Misses       11616    11615    -1     

Components	Coverage Δ
cvat-ui	77.22% <85.71%> (+0.01%)	⬆️
cvat-server	71.63% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bsekachev]

LGTM as fix

However I would propose to get rid of triggering resize event on windows as potentially it may lead to unnecessary layout changes in other UI elements.

My idea here is to wrap onResize with useCallback depending on fitCanvas.
And wrap setLayoutConfig calling this callback in zero setTimeout after setting the state. Not sure about if we really need setTimeout. As this is not related directly to this PR is up to you to implement or not.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud