Added missing channel devices

Implement RG32UI and R32UI

audio_core: Interpolate

arm_dynarmic: Remove IsExecuting check from PrepareReschedule

maxwell_to_gl: Implement VertexAttribute::Size::Size_8.

No longer required. HaltExecution is a no-op if it is not currently executing.

Needed for xenoblade

vfs: Use sanitized paths within MoveFile() and MoveDirectory()

card_image: Simplify return statement of GetSubdirectories()

kernel/object: Tighten object against data races

- Used by Breath of the Wild.

renderer_opengl: Implement RenderTargetFormat::RGBA16_UINT.

Despite being covered by a global mutex, we should still ensure that the
class handles its reference counts properly. This avoids potential
shenanigans when it comes to data races.

Given this is the root object that drives quite a bit of the kernel
object hierarchy, ensuring we always have the correct behavior (and no
races) is a good thing.

- Used by Breath of the Wild.

renderer_opengl: Implement RenderTargetFormat::RG8_UNORM.

maxwell_to_gl: Implement PrimitiveTopology::LineStrip.

- Used by Breath of the Wild.

- Used by Breath of the Wild.

Use an approximated amortized amount of ticks when advancing timing.

scheduler: Make HaveReadyThreads() a const member function

Fixed a bunch of race conditions when running in multicore mode.

Kernel/Mutex: Don't duplicate threads in the mutex waiter list.

gl_shader_decompiler: Implement XMAD instruction.

We divide the number of ticks to add by the number of cores (4) to obtain a more or less rough estimate of the actual number of ticks added. This assumes that all 4 cores are doing similar work. Previously we were adding ~4 times the number of ticks, thus making the games think that time was going way too fast.

This lets us bypass certain hangs in some games like Breath of the Wild.

We should modify our CoreTiming to support multiple cores (both running in a single thread, and in multiple host threads).

The current core may have nothing to do with the core where the new thread was scheduled to run. In case it's the same core, then the following PrepareReshedule call will take care of that.

Another thread may write to this variable while the core in question is in the middle of checking for a reschedule request.

Another thread might be in the middle of an SVC, thus altering the state of the schedulers.

Another thread might be in the middle of a reschedule, thus altering the state of the schedulers.

WakeAfterDelay might be called from any host thread, so err on the side of caution and use the thread-safe CoreTiming::ScheduleEventThreadsafe.

Note that CoreTiming is still far from thread-safe, there may be more things we have to work on for it to be up to par with what we want.

vfs: Make type hierarchy objects classes instead of structs

Exit from AddMutexWaiter early if the thread is already waiting for a mutex owned by the owner thread.

This accounts for the possibility of a thread that is waiting on a condition variable being awakened twice in a row.

Also added more validation asserts.

This should fix one of the random crashes in Breath Of The Wild.

Makes it consistent with the other VFS interfaces and prevents implicit
construction.

struct should be used when the data type is very simple or otherwise has
no invariants associated with it. Given these are used to form a
hierarchy, class should be used instead.