Xbox controller default name nit pick

input_common: Reintroduce motion from mouse and use button names

Accurately implement thread exit

astc_decoder: Combine FastReplicate functions to work around new NV driver bug

kernel: remove no-op code

input_common: nitpick about SetHatButton usage

input_common: fix copy-paste error

hid: fix std::transform call

hid: Correct assignment source for rotations

Found by static analysis with PVS-Studio. Nobody seems to really know what was it doing there.

Change default theme to Dark colorful

Found by static analysis with PVS-Studio.

Found by static analysis with PVS-Studio.

Eliminates the usage of a magic number to indicate the default index of the themes array,

Found by static analysis with PVS-Studio

The new Nvidia drivers have a bug where the FastReplicateTo6 function produces a lookup into the REPLICATE_TO_8 table rather than the REPLICATE_TO_6 table.

This seems to be an optimization gone wrong. Combining the logic of the FastReplicate functions seems to address the bug.

Discord User moon lacer pointed us that official name is 'Xbox' not 'XBox'

Change default name for playstation controllers

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

Minor nitpick
Code is from narr

service/hid: Decrease motion update rate

- This is used to terminate a thread asynchronously after it has been exited.
- This fixes a crash that can occur in Pokemon Sword/Shield because a thread is incorrectly closed on svcExitThread, then, the thread is destroyed on svcCloseHandle while it is still scheduled.
- Instead, we now wait for the thread to no longer be scheduled on all cores before destroying it from KWorkerTaskManager, which is accurate to HOS behavior.

- This makes our implementations of these more closely match HOS.

- These primitives are used to dispatch asynchronous kernel tasks from KThread and KProcess.

- When the emulator crashes to desktop below, we don't even get this captured in a log, making such issues harder to debug.

- 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

Motion stops working in Mario Tennis in swing mode if the update rate is too fast even when HW it updates at the same speed. 10ms it's the minimum period that the game needs to start working again.

cmake: make tests optional