main: Make separate render window fullscreen toggle on the monitor it resides in

Allow overriding SCM version info

service/hid: Improve console motion accuracy

dist/XDG: add more file associations

If the build is from a non-repository, these functions will return empty. This
patch allows using defines to CMake to set version info such as
-DGIT_BRANCH=master.

core: hle: Remove global HLE lock.

kernel: Manually destroy the current process during shut down

Toggling borderless fullscreen on the separate render window made it fullscreen on the monitor which the main yuzu window resided in.

This change allows the render window to go fullscreen on the monitor it resides in, independent of the main window location.

Avoids a memory leak.

core/hid: Cancel any vibration after the test

core: loader: kip: Minimal changes to fix KIP loading.

[Patch v2] externals/ffmpeg: refactor ffmpeg searching and handling in cmake

externals/CMakeLists: fix detection/init of Switch controllers in SDL 2.0.18

[input_common] Fixed thread hang

- Allows us to boot KIP (kernal apps), useful for testing the kernel.

video_core: Refactoring post A.R.T. merge

game_list: Add persistent setting for the favorites row expanded state

- This was added early on as a hack to protect against some concurrency issues.
- It's not clear that this serves any purpose anymore, and if it does, individual components should be fixed rather than using a global recursive mutex.

MSVC supplied with VS2022 generates "warning C4189: 'CALIBRATION_THRESHOLD':
local variable is initialized but not referenced" which is treated as an
error.

Circumvent it by moving constexpr variable directly into body of lambda function.

Enable SDL_THREADS and SDL_ATOMIC
Also set SDL_WAYLAND=OFF due to build issue

Closes #7572

Update video core popup

Fix blit image/view not compatible

... to avoid leaving variable undefined in the current scope

yuzu/main: Fix host memory byte units. GB to GiB

Revert "video_core/codecs: refactor ffmpeg searching and handling in cmake"

I have `134850146304` bytes of ram and Yuzu was saying that I had `125.59 GB`
of ram. But `125.59` is actually the amount of gi**bi**bytes I have. In
gi**ga**bytes I would have `134.9`.

Additionally, I changed the `1024 / 1024 / 1024` here into the `_GiB`
user-literals that I added a while ago(#6519).

https://www.wolframalpha.com/input/?i=134850146304+bytes

video_core/codecs: refactor ffmpeg searching and handling in cmake

common/cpu_detect: Remove CPU family and model

maxwell_to_vk: Add ASTC_2D_8X5_UNORM

qt_software_keyboard: Fix out of bounds array access

core/hid: Fix faulty analog triggers