Elevated profile doesn't open Quake terminal

[elsaco]

Windows Terminal version

main 7061c54

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

• add new profile and set "elevate": true
• open new profile
• close previous terminal window
• open Quake terminal

Expected Behavior

• quake mode terminal

Actual Behavior

• no quake mode terminal window:

[zadjii-msft]

This is likely what happened

1. You started the terminal, and it took the win+` hotkey
2. You started an elevated terminal. It trued to take the win+` hotkey, but found it was already bound, so it failed.
3. You closed the unelevated Terminal. Nothing here tells the elevated Terminal to take over the keyboard shortcuts
4. You press win+`, but no one has that key bound.

I suspect this isn't the only time we're going to hear this on this release. Not sure what a good solution is. Maybe an elevated flag to globalSummon, as a bool?, that can filter to {any window, unelevated only, elevated only}?

This would be the release to handle this, that's for sure.

[User1785604260]

Coming here from #9996. I'd like to have a way to enforce that the new headless terminal from #14944 is the only thing registering the Win+` quakeMode hotkey. This is so that I can ensure quakeMode windows are always unelevated (my preference) by launching the headless terminal as unelevated.

As it currently stands, there's a race as too which terminal starts first and captures the hotkey. If I open an elevated terminal immediately on login, I can find myself locked into elevated-only quakeMode terminals.