FEAT(client): Implemented new Global Shortcuts

[Globostofo]

As mentionned in #6229, this commit implements new global shortcuts linked to the menu actions. The following actions are now available:

• Connect to a server
• Disconnect from server
• Open server information
• Open server tokens
• Open server user list
• Open server ban list
• Toggle priority speaker
• Open recording dialog
• Change comment
• Change avatar
• Remove avatar
• Register on the server
• Audio statistics
• Open settings
• Start audio wizard
• Start certificate wizard
• Toggle TTS
• Open about dialog
• Open about Qt dialog
• Check for update

Implements #6229

Checks

• My commits follow the commit guidelines

[Globostofo]

I'm completely open to your recommendations and changes.
I'm not a native English speaker, so don't hesitate to correct me if you see any mistakes in my code (strings or variable/method names).

Thank you in advance for your consideration :^)

[Hartmnt]

Thanks for your contribution! I will look into this in more detail soon.
Just skimming over the new actions, would you also be able to implement #3932 ? That is actually a feature request we received multiple times. But it would require you to add user data similar to the whisper/shout shortcut. Maybe that is out of the scope of this MR 🤔

Anyway, the checks are currently failing for a few code formatting issues. You can check the logs of the "PR-Checks" run. Do not worry about the translation check failing that can be fixed when everything else is done :)

Edit: Feel free to ask if you need help updating the existing pull request using git. Quite a few people have trouble with that at first.

[Globostofo]

Thanks for your feedback!

After taking a look at the issue you're talking about and the code it would require to modify, I think it's out of the scope of this MR whose goal is the implementation of new shortcuts. However, I'll be happy to work on it once this MR is closed :^)

I'll start solving the check problems right away 👍. Would you prefer me to create a new commit on my branch or amend the one I've already done?

[Hartmnt]

I'll start solving the check problems right away 👍. Would you prefer me to create a new commit on my branch or amend the one I've already done?

In the end we want one commit for your cumulative changes and one translation commit. So amending the fixes into your existing commit would be the way to go right now.

[Globostofo]

I've patched the formatting errors, but I'm not sure what to do in the translation commit you mentioned. Can you explain?

[Hartmnt]

Can you explain?

Mumble translations are community contributions outside of the Mumble GitHub repository. To enable the translations for new strings, you will have to add a "translation commit" using the scripts located in this repo. They will perform all the necessary steps to get the new strings up for translation automagically.

You can add the translation commit now, but remember: if someone reviews this MR and tells you there is some more work to do, you will have to squash that changes into your existing commit (amending will not work that easy, because the translation commit will be the last). But if you feel good about your git skills, you can run the updatetranslations.py script in the scripts folder from the repository root now. Alternatively, just wait for the reviews and if there are no more complaints you can add the translation commit last.

[Krzmbrzl]

LGTM - I assume that you have also verified that these new shortcuts work as expected and that the menu controls also still work as expected? If so, then please add the translations commit now (if you prefer I can also add it for you) and then this can be merged.

[Globostofo]

Yes of course, I've tested all the shortcuts I've implemented. I did my best to avoid bugs, but if anyone finds a problem in the future, please let me know so I can help fix it :^)

[Krzmbrzl]

Awesome! Thank you very much! 👍