Maximising Frame Debugger window forces target process to Editor

Steps to reproduce:

1. Open the attached project
2. Open Frame Debugger window (Window -> Analysis -> Frame Debugger)
3. Build and launch a Standalone build with Development mode enabled (Attached project already contains a ready macOS build)
4. In the Frame Debugger window, set the Target process to the standalone build
5. Enable Frame Debugging to gather data
6. Double-click on the Frame Debugger window or use the Right-Click menu to maximise the window
7. Observe the Frame Debugger window

Actual results: Frame Debugger's target process is forced to Editor, and the data disappears after the window is maximised

Expected results: Target process remains set to the standalone build, and data persists after maximising the Frame Debugger window

Reproducible with versions: 6000.3.0a1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2

Not reproducible with versions: 6000.0.63f1, 6000.2.14f1

Tested on (OS): macOS 26.1, Ubuntu 24.04