Qt: Don't contain display surface when render to separate or fullscreen is used on Windows
Description of Changes
On Windows, we don't contain DisplaySurface, in render to separate or full-screening its container.
Rationale behind Changes
DX11 & DX12 refuse to fullscreen with the current setup, they seem to require the surface be the top-level window when fullscreened.
QWindow doesn't get Client side decorations on Wayland, and I don't have a Mac to test on, so these changes are currently Windows only
None windows platforms continue to use a container for fullscreen.
Suggested Testing Steps
Test fullscreen. Test exiting in and out of fullscreen. Test render to separate window. Test receiving popups during rendering while fullscreened. Retest with Render to separate window. Test if there are new frame pacing or latency issues while fullscreened.
The behaviour changes are Windows focused, but a test for other platforms is needed to make sure nothing broke.
Did you use AI to help find, test, or implement this issue or feature?
No
Does VRR work on AMD with a maximized container? iirc, Freesync (on AMD) only works will full screen applications, where Nvidia can do windows and full screen. Emulation is definitely made better by VRR :)
Edit: I've been told VRR apparently works in borderless/window mode on AMD now, but getting super conflicting info online.
There's also exclusive full screen to consider (a bunch of people will lose their crap if that no longer works lol).
Moved the fix for selecting which screen for exclusive fullscreen over to #13644 as I felt it was more relevant for that pr instead of this one