fix(chat): Edit last message hotkey on macOS

[ShGKme]

☑️ Resolves

• Follow-up: The shortcuts use the control (^) button on macOS instead of the command (⌘) button #13654
• Ctrl+⬆️ is a system hotkey on Mac and doesn't work as web-page hotkey
  • Added Cmd(Meta)+⬆️
• Also fixed hotkeys in the help in the settings dialog

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

🏚️ Before	🏡 After

🏁 Checklist

• 🌏 Tested with different browsers / clients:
  • Chromium (Chrome / Edge / Opera / Brave)
  • Firefox
  • Safari
  • Talk Desktop
  • Not risky to browser differences / client
• 🖌️ Design was reviewed, approved or inspired by the design team
• ⛑️ Tests are included or not possible
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

[ShGKme]

/backport to stable30

[Antreesy]

meta is a 'Windows' key also. maybe replace it with useHotKey()?

[ShGKme]

meta is a 'Windows' key also

It is not a problem, it is ignored on Windows and, afaik, all (most?) Linux DEs (Checked on GNOME, KDE, xfce, Cinnamon)

maybe replace it with useHotKey()?

I'd avoid having a global listener here

[ShGKme]

Update: xfce handles meta key with default settings.

But this doesn't lead to an issue:

• If a user has desktop environment to handle this hotkey, e.g., for window management - it has no affect in talk
• If a user doesn't have it in DE, and presses this hotkey while the focus is in the message input - it enables the last message editing
  • In the best case - a user get used to macOS is happy
  • In the worst case - some other (bot not desktop environment level) hotkey lead to a harmless action in talk - edit mode

[Antreesy]

Shouldn't we update in the meantime?
https://docs.uaparser.dev/intro/whats-new.html#version-2-0

[ShGKme]

We can

[Antreesy]

Then let's follow-up, if you don't want to mix PRs

[DorraJaouad]

Tested on Windows (at least it's confirmed that it remains working for Win :') )

[ShGKme]

/backport to stable30

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/13658/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick cdc937ee 76d88fd8 64622149 fa2a3498 a8e04e76

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/13658/stable30

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/13658/stable30."}

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[ShGKme]

/backport to stable30.0