[Peek] Fix idle CPU usage

[davidegiacometti]

Summary of the Pull Request

• The idle CPU usage happen when the window is initialized without activation. A thread hang wasting CPU cycles until the window is initialized

0.75

0.0.1

• Can't really see the CPU usage on my workstation but I have notices the battery/CPU usage on a laptop when I barely use Peek (probably due to smaller CPU compared to the workstation). The incriminated thread is present on both machines.

0.75

0.0.1

PR Checklist

• Closes: Peek: High CPU usage when no monitor connected #27294
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

• Moved the event that listen the Peek hotkey from window level to app level
• Instantiate the window when Peek is invoked for the first time

Validation Steps Performed

• A local build has been tested successfully by some users that reported the issue: Peek: High CPU usage when no monitor connected #27294 (comment)
• Tested the local build on 2 machines: Peek working as expected and no incriminated thread or CPU usage before invoking Peek for the first time

[jaimecbernardo]

LGTM! Only create resources when used seems like a good change. All the better if it fixes the weird CPU issue.
Thank you for the contribution!