- PR #7699 attempted to fix CreateServiceThread and ReleaseServiceThread to be thread safe, but inadvertently introduced a possible dead-lock.
- With this PR, we use a worker thread to manage the service thread list, allowing it only to be accessed by a single thread, and guaranteeing threads will not destroy themselves.
- Fixes a rare crash in Pokemon Sword/Shield, I've now run this game for ~12 hours non-stop and am quite confident this is a good solution for this issue.

hle: kernel: Fix service_threads access to be thread safe.

Kernel Memory Updates (Part 2): SetProcessMemoryPermission, update permissions, and other minor changes.

- CreateServiceThread and ReleaseServiceThread can be accessed by different threads, uses a lock to make this thread safe.
- Fixes a rare crash in Pokemon Sword/Shield that can occur when a new service thread is being created while an old one is being destroyed.

yuzu: main: Increase the open file limit on Windows to 8192

core/hid: Reduce gyro threshold even more

cmake: make tests optional

Kernel Memory Updates (Part 1): SetMemoryAttribute, and other minor changes.

yuzu: Add controller hotkeys

This is a temporary solution for now to accommodate for mods containing more than 4096 files.

logging: adapt to changes in fmt 8.1

input_common: Handle errors on TAS scripts

... to common/logging/formatter.h

... requirements for fmt stays at ^8.0.1

input_common: Fix UDP controller mappings

input_common: Allow to only have acceleration motion data

video_core/memory_manager: Fixes for sparse memory management

externals/dynarmic: update to the latest revision

... to resolve compilation errors with fmt 8.1

configure_per_game: Initialize tabs after loading custom configuration

glsl: Remove unreachable return

Update translations (2022-01-05)