gl_shader_decompiler: Rename cc to condition code and name internal flags

shader_cache: Only lock covered instructions.

software_keyboard: Minor changes

applets: Add StubApplet and use it as fallback when AppletId is not implemented

core: Relocate CPU core management to its own class

common/thread: Minor cleanup

* Added predicate comparison LessEqualWithNan

* oops

* Clang fix

gl_shader_decompiler: Fix register overwriting on texture calls

Properly Implemented TXQ Instruction

nvhost_ctrl_gpu: Implement IoctlGetGpuTime.

debug_pad: Avoid loading input for nonexistent buttons (Home and Screenshot)

Prevents memory exceptions when the debug pad is enabled.

maxwell_3d: Implement alternate blend equations.

audout_u: Add support for multiple IAudioOut streams.

macro_interpreter: Implement AddWithCarry and SubtractWithBorrow.

Keeps the CPU-specific behavior from being spread throughout the main
System class. This will also act as the home to contain member functions
that perform operations on all cores. The reason for this being that the
following pattern is sort of prevalent throughout sections of the
codebase:

If clearing the instruction cache for all 4 cores is necessary:

Core::System::GetInstance().ArmInterface(0).ClearInstructionCache();
Core::System::GetInstance().ArmInterface(1).ClearInstructionCache();
Core::System::GetInstance().ArmInterface(2).ClearInstructionCache();
Core::System::GetInstance().ArmInterface(3).ClearInstructionCache();

This is kind of... well, silly to copy around whenever it's needed.
especially when it can be reduced down to a single line.

This change also puts the basics in place to begin "ungrafting" all of the
forwarding member functions from the System class that are used to
access CPU state or invoke CPU-specific behavior. As such, this change
itself makes no changes to the direct external interface of System. This
will be covered by another changeset.

- Used by Undertale.

- Used by Undertale.

- Used by Undertale.

This is inconsistent with our coding style.

Implemented Fast Layered Copy

common: Remove bit_set.h

kernel/handle_table: Minor changes

While admirable as a means to ensure immutability, this has the
unfortunate downside of making the class non-movable. std::move cannot
actually perform a move operation if the provided operand has const data
members (std::move acts as an operation to "slide" resources out of an
object instance). Given Barrier contains move-only types such as
std::mutex, this can lead to confusing error messages if an object ever
contained a Barrier instance and said object was attempted to be moved.

Simplifies the constructor interfaces for Barrier and Event classes.

Keeps the non-member interface in one spot instead of split into two
places, making it nicer to locate functions.

This is also unused and superceded by standard functionality. The
standard library provides std::this_thread::sleep_for(), which provides
a much more flexible interface, as different time units can be used with
it.

This is an old function that's no longer necessary. C++11 introduced
proper threading support to the language and a thread ID can be
retrieved via std::this_thread::get_id() if it's ever needed.

This is an analog of BitSet from Dolphin that was introduced to allow
iterating over a set of bits. Given it's currently unused, and given
that std::bitset exists, we can remove this. If it's ever needed in the
future it can be brought back.

This will log all data it receives, log all calls to its methods and push dummy data into both channels on execution.

These don't depend on class state, and are effectively implementation
details, so they can go into the cpp file .

The previous handle table size is a holdover from Citra. The actual
handle table construct on Horizon only allows for a maximum of 1024
entries.

We don't need to potentially inline the teardown logic of all of the
handle instances.

Use default values for unknown framebuffer pixel format

gl_shader_decompiler: Use UNIMPLEMENTED when applicable