Game Window not resizing correctly (when AdaptBackBufferToScreen is set)

Release Type: Official Release (4.1.0.1459-beta, .Net 5.0.8)

Version: ^^^

Platform(s): Windows Desktop build

Describe the bug
When attempting to resize the game window (in windowed mode), the expected default behaviour of resizing does not occur, and the window will change it's size/position in ways it shouldn't (because something else was being changed)

To Reproduce
Steps to reproduce the behavior:

1. Build any project and run it (Debug/Release are the same)
2. Attempt to resize the game window that appears

Expected behavior
The window expands/contracts in the way that was desired. E.g. If dragging the right side of the window, it should increase in width, and have no other changes.

Actual Behaviour
The game window does 'funky shit' that is completely wrong. Things I have experienced:

1. When attempting to make the window wider, the width stays the same, but the height shrinks instead (so the aspect ratio I was trying to get would probably be correct, but it changed the wrong thing)
2. Same thing for the height
3. The game window sets itself to 4k resolution, despite me being on a 1080p monitor.
4. The window will forcibly set it's width (and I believe height too sometimes) to a number when I attempt to resize that seems reasonably close to 4k resolution

Screenshots

1. Log of screen dimensions It should be noted that I never made the window larger in any dimension (not purposefully), just tried to shrink it and move it. It enlarged itself on it's own
2. Recording of me testing code. Some things to note:
   • Flags 1-4 are me manually enlarging/shrinking the window via code using a loop, this works as expected
   • Flag 5 is 'no behaviour', where I disable my code and let Stride do it's own thing. It seems that changing the height seems to mostly work, but changing the width messes everything up. Also the 4k thing I mentioned happens several times, as well as the window being a completely different size to what it's supposed to be.
   • Flag 6 is my attempt at fixing it by forcibly setting the window size to what it's supposed to be (Window.SetSize(Window.PreferredWindowedSize);). This seems to work because, like i noted before, setting the dimensions from code works fine, it's just the user part that's broken

Log and callstacks
N/A AFAIK

Additional context
When changing the resolution and or position via code, the window appears to act normally - the issue appears to be only through user interaction.

Reproduce the issue in a Windows Desktop build with AdaptBackBufferToScreen enabled, following the resize steps and comparing user resizing with Window.SetSize(Window.PreferredWindowedSize). Trace the window-resize path and verify that dragging each edge changes only the intended dimension without forcing an incorrect size or resolution.