Fixup! #2772 missed this one file

Port citra-emu/citra#4849: "Qt: Fixed behaviour of buttons by connecting functors to correct signals"

yuzu/CMakeLists: Remove qt5_wrap_ui macro usage

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

ci: Fix Azure PR Builds

Implement GPU Synchronization Mechanisms & Correct NVFlinger

video_core/control_flow: Minor changes/warning cleanup

Shader_Ir: Correct tracking to track from right to left

yuzu/main: Make error messages within OnCoreError more localization-friendly

Downgrade and suppress a series of GPU asserts and debug messages.

maxwell3d: Implement Conditional Rendering

Fix README change mistake

gl_rasterizer: Implement compute shaders

Rework Dirty Flags in GPU Pipeline, Optimize CBData and Redo Clearing mechanism

shader/half_set_predicate: Implement missing HSETP2 variants

azure: Fix clang-format and releases

Provides operational symmetry for the respective structures.

The return value is a u32, not an s32, so this would result in an
implicit signedness conversion.

This is the default behavior of the copy constructor, so it doesn't need
to be specified.

While we're at it we can make the other non-default constructor
explicit.

Results in less work being done where avoidable.

Same thing, but potentially allows a standard library implementation to
pick a more efficient codepath.

It's what it's there for.

Ensures that the constructor members are always initialized in the order
that they're declared in.

Prevents a truncation warning from occurring with MSVC. Also the
internal data structures already treat it as a size_t, so this is just a
discrepancy in the interface.

Previously, quite a few functions were being linked with external
linkage.