The speed limiter being a frame limiter is an implmentation detail and can be changed in the future. What user care about is that it limit the emulation speed in genenral (not just graphics but also audio+input)

Co-Authored-By: Weiyi Wang <wwylele@gmail.com>

Ported from https://github.com/citra-emu/citra/pull/3617.

I missed this in my original PR (https://github.com/yuzu-emu/yuzu/pull/1886).

Co-Authored-By: Vitor K <vitor-k@users.noreply.github.com>

We can simply enable CMAKE_AUTOUIC and let CMake take care of handling
the UI code generation for targets.

As part of letting CMake automatically handle the header file parsing,
we must not name includes with "ui_*" unless they're related to the
output of the Qt UIC compiler. Because of this, we need to rename
ui_settings, given it would conflict with this restriction.

Following screens got fixes:
- Configure/Debug
- Configure/Input

The JIT is mature enough that this setting can be removed, falling back
to Unicorn only on unsupported architectures. Any missing features from
Unicorn (of which there are extremely few), are mostly
developer-oriented, which most users don't care about.

Features should be coordinated with the JIT, not the interpreter,
anyhow.

A normal user shouldn't change this, as it will slow down the emulation and can lead to bugs or crashes. The renaming is done in order to prevent users from leaving this on without a way to turn it off from the UI.

To prepare for translation support, this makes all of the widgets
cognizant of the language change event that occurs whenever
installTranslator() is called and automatically retranslates their text
where necessary.

This is important as calling the backing UI's retranslateUi() is often
not enough, particularly in cases where we add our own strings that
aren't controlled by it. In that case we need to manually refresh the
strings ourselves.

Fixes #2522.

Also cleanup of general stuff

Reports are unnecessary for normal users and this is to prevent 'power' users from enabling the feature by accident.

Full enable/disable for all reports.

Nothing from the hotkeys dialog relies on this call occurring, and is
already called from the dialog that calls applyConfiguration().

Avoids mentioning the user and formalizes the error itself.

critical() is intended for critical/fatal errors that threaten the
overall stability of an application. A user entering a conflicting key
sequence is neither of those.

We don't need to extract the entire set of hotkeys into a list and then
iterate through it. We can traverse the list and early-exit if we're
able to.

1. This is something that should be solely emitted by the hotkey dialog
itself
2. This is functionally unused, given there's nothing listening for the
signal.

A checkbox is able to be tri-state, giving it three possible activity
types, so in the connect call here, it would actually be truncating an
int into a bool.

Instead, we can just listen on the toggled() signal, which passes along
a bool, not an int.

Given the array is a private static array, we can just make it
internally linked to hide it from external code. This also allows us to
remove an inclusion within the header.

Allows the configuration code to build successfully with implicit string
conversions disabled.

Allows the web config code to compile with implicit string conversions
disabled. We can also deduplicate the calls to create the pixmap.

Allows the system config code to build successfully with implicit string
conversions disabled.

This is a user-facing string, so it should be marked as translatable.

Allows the per-game configuration to be successfully built with implicit
string conversions disabled.

Deduplicates array accesses and uses a named variable where appropriate.

Allows the advanced mouse configuration code to build with implicit
string conversions disabled.

Rather than repeatedly index arrays that have quite a large array index,
we can just use a named variable instead.

Allows the player input configuration code to compile with implicit
string conversions disabled.