The IR expects GetAttribute to return an F32 value. This case was returning a U32 instead.

vulkan_device: Add a check for int8 support

GPU_MemoryManger: Fix GetSubmappedRange.

logging: Fix log filter during initialization

Silences validation errors when shaders use int8 without specifying its support to the API

The log filter was being ignored on initialization due to the logging instance being initialized before the config instance, so the log filter was set to its default value.

This fixes that oversight, along with using descriptive exceptions instead of abort() calls.

kernel: Optimize GetHostThreadID

CMakeLists: Ensure proper numerusform tags are generated for pluralized translations

logging: Simplify and make thread-safe

If we don't set an explicit source and target language for the base
english translation, then we'll generate an incorrect number of
<numerusform> tags (which Transifex doesn't like).

settings: Amend language_index maximum setting range

The maximum is now 17 with the addition of Brazilian Portuguese

video_core: eliminate constant ternary

dynarmic: Update and enable DYNARMIC_IGNORE_ASSERTS

SPIR-V: Merge two ifs in EmitGetAttribute

applet_error: Fix 64-bit error code conversion

Replace QPoint with QPointF where applicable

Previously, floats were implicitly cast to integers

qt_software_keyboard: fix copy-paste error

`via_header_index` is already checked above, so it would never be true in this branch

Fix crash in logging in CreateStrayLayer

It was trying to log value of layer_id which is specifically known not to exist, potentially leading to segfault. Log display_id instead.

Fix check is thread current in GetThreadContext

Misplaced break made it only check for the first core.

kernel: Various improvements to scheduler

Fix LAN Play

decoders: Optimize memcpy for the other functions

threadsafe_queue: Fix deadlock

- This would have limited value, and would be a mess to handle properly.

This fixes a lost wakeup in SPSCQueue. If the reader is in just the right position, the writer's notification will be lost and this will be a problem if the writer then does something to wait on the reader.

This was discovered to affect my upcoming stacktrace PR. I don't think any performance decrease will be noticeable because an uncontended mutex is smart enough to skip the syscall. This PR might also resolve some rare deadlocks but I don't know of any examples.