Ensure windows are visible when recovering a session

[romanroibu]

This PR fixes issues related to windows being outside the display bounds when recovering a session.

[romanroibu]

@papr @pfaion The implementation currently in this PR tests if the origin of the window is within any of the connected monitors. This, however, can lead to situations where even windows with as little as 1 pixel (origin) within the monitor keep their position. I was thinking about an alternative implementation where we would calculate an intersection rectangle of the window and each monitor. The rectangle would be valid if it's at least 10x10 pixels (or any other size). If there are no valid rectangles - the position is reset to default. Wanted to see what you think about current and proposed implementations.

[papr]

I like the idea about the intersection area. But since windows are only movable if their "header" is clickable, I suggest applying your logic such that the header has a minimum visible area before resetting the window to its default position.

[papr]

@pfaion Please give this recovery logic a try on Windows. Please try it with different multi-screen setups, i.e. disconnected screen to the left/top/bottom/right.

[romanroibu]

@papr @pfaion I incorporated all the latest feedback. Please let me know if there's anything else that might need changing.

[papr]

When I was suggesting to use typing.NamedTuple, I was mostly referring to using the type annotation possibility to define the tuple, making it more readable. Please adopt the type annotation variant accordingly.

[pfaion]

Works fine in different window layouts!