Modernize cursor update for the game area

[Districh-ru]

Based on #7808.

This PR does the next changes:

• fixes Map Editor, cursor issues after info window appears #8026;
• pass gameArea to the QuickInfo() functions;
• restore cursor immediately after the Quick Info dialog is closed if no cursor change is predicted;
• schedule immediate cursor update after Quick Info dialog is closed;
• set POINTER cursor when map dragging is started (it is made to show the player that no action will be performed after the mouse button is released, discussible, can be reverted);
• add forced software cursor render on the screen after cursor icon is updated;
• remove the forced cursor update setting on every CURRENT_HERO_DELAY pass: this part needs testing, the assertions are temporary put instead;
• schedule the cursor update after Puzzle or View World dialog is closed;
• make View World use reference to the gameArea of given interface (AdventureMab/EditorInterface);
• do not make gameArea copies for the View World, use references to the original gameArea.

[Branikolog]

Everything works fine.
However, this PR does not fix #8026.

[ihhub]

I am moving this change to the next release as we are very close to the current release.

[ihhub]

Hi @Districh-ru , I put several comments in this pull request. Would you mind to take a look at them?

[ihhub]

I can see that we set to update cursor if Interface::REDRAW_RADAR_CURSOR flag is set. Is it valid for all situations? If yes should we add an internal logic while redrawing adventure map to update the cursor?

[Districh-ru]

Hi, @ihhub, you are right - REDRAW_RADAR_CURSOR is not needed here because we restore radar by restorer. I made the same restorer for the second puzzle function. It was called here to restore radar because its area is used to render EXIT button.

[ihhub]

Hi @Districh-ru , do we need to change specific logic in this pull request since we separated Adventure Map and Editor classes and do not share quick info dialog code for the Editor?

[Districh-ru]

Hi @Districh-ru , do we need to change specific logic in this pull request since we separated Adventure Map and Editor classes and do not share quick info dialog code for the Editor?

Hi @ihhub, yes this PR needs some improvement for the new editor quick view. I'll update it on the next week.

[Districh-ru]

Some parts of this PR are redone in separate PRs.
QuickInfo() was reworked recently and needs many conflicts to resolve.
Besides the approach in this PR is not perfect and involves many duplications and the need to transfer the gameArea instance to the QuickInfo() functions.
I'm closing this PR and will open a new one to fix QuickInfo() cursor update after I test another approach.