The latest git version of GCC has issues with my diamond inheritance
shenanigans. Since that's now two compilers that don't like it I thought
it'd be best to just axe all of it and just have the two templates like
before.

This rolls the features of BasicRangedSetting into BasicSetting, and
likewise RangedSetting into Setting. It also renames them from
BasicSetting and Setting to Setting and SwitchableSetting respectively.
Now longer name corresponds to more complex thing.

Replace multiple names with a better name

Support `InfoType_MesosphereCurrentProcess`

kernel: make current thread pointer thread local

Co-authored-by: liamwhite <liamwhite@users.noreply.github.com>

gdbstub: fix register pokes

KPageTable: Remove extraneous assert

kernel: wait for threads to stop on pause

Since start is always 0 and VAddr is unsigned, we can safely remove this assert.

ci/windows: Use Clang for MinGW builds

core/debugger: memory breakpoint support

kernel: fix some uses of disable_count

service: am: Stub PerformSystemButtonPressingIfInFocus

Used by Ring Fit Adventure

core: fix initialization in single core, sync GPU mode

Uses the MinGWClangCross toolchain script to build yuzu. Disables our
bundled SDL2 to use the system ones that have been modified to not use
`-mwindows`. Also set's `-e` to stop the script on an error (as opposed
to packaging nothing).

Uses LLVM's linker for linking yuzu. Adds -femulated-tls due to a
libstdc++ incompatibility between GCC and Clang in vulkan_common.

Facilitates what programs we need for cross-compiling to Windows from
Linux using LLVM's compilers. Based on MinGWCross

Improves readability.

common: param_package: Demote DEBUG to TRACE for getters

Make yuzu-cmd respect log_filter setting

Because logging infrastructure initializes before the loading of the
config, it reads the default setting for log_filter and ignores the one
set in config. To change log_filter after logging initialization some
additional calls need to be made.

Implement ExitProcess svc

Currently this just stops all the emulation
This works under assumption that only application will try to use
ExitProcess, with services not touching it
If application exits - it quite makes sense to end the emulation