fix(core): don't hijack Ctrl+F in editors or behind modals

[pringelmann]

• Resolves: Search for word inside page is impossible #63409

Summary

Unified search bound its own keydown listener that never checked the event target or open modals, so Ctrl+F inside a Text document opened search instead of the browser's find bar. useHotKey already guards both, so this uses it instead of duplicating that logic in core.

Behaviour changes

• Ctrl+F in an editor or input now goes to the browser. Same behind an open modal.
• Ctrl+K works again on /settings/users, /settings/apps and /apps/deck. It was checking the Ctrl+F opt-out, which nothing on that list uses for Ctrl+K, so Firefox took the key. Pre-existing bug.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes (no visual change)
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI (tests, reviewed by me)

[pringelmann]

/backport to stable34

[pringelmann]

/compile rebase