Moves the memory writes directly into QueryProcessMemory instead of
letting the wrapper function do it. It would be inaccurate to allow the
handler to do it because there's cases where memory shouldn't even be
written to. For example, if the given process handle is invalid.

HOWEVER, if the memory writing is within the wrapper, then we have no
control over if these memory writes occur, meaning in an error case, 68
bytes of memory randomly get trashed with zeroes, 64 of those being
written to wherever the memory info address points to, and the remaining
4 being written wherever the page info address points to.

One solution in this case would be to just conditionally check within
the handler itself, but this is kind of smelly, given the handler
shouldn't be performing conditional behavior itself, it's a behavior of
the managed function. In other words, if you remove the handler from the
equation entirely, does the function still retain its proper behavior?
In this case, no.

Now, we don't potentially trash memory from this function if an invalid
query is performed.

These should be swapped.

The kernel returns a memory info instance with the base address set to
the end of the address space, and the size of said block as
0 - address_space_end, it doesn't set both of said members to zero.

Gets rid of the need to directly access the managed VMAs outside of the
memory manager itself just for querying memory.

Gets the two structures out of an unrelated header and places them with
the rest of the memory management code.

This also corrects the structures. PageInfo appears to only contain a
32-bit flags member, and the extra padding word in MemoryInfo isn't
necessary.

Amends the MemoryState enum to use the same values like the actual
kernel does. Also provides the necessary operators to operate on them.
This will be necessary in the future for implementing
svcSetMemoryAttribute, as memory block state is checked before applying
the attribute.

file_sys/directory: Amend path buffer size for directory entries

patch_manager: Add support for disabling patches

Port citra-emu/citra#4476: "web_service: move telemetry condition from TelemetrySession constructor to destructor"

service/fsp_srv: Correct returned value in GetGlobalAccessLogMode()

file_sys/save_data_factory: Update SaveDataSpaceId enum

Implemented Shader Unique Identifiers

kernel/process: Set ideal core from metadata

savedata_factory: Add CacheStorage and delete TemporaryStorage on boot

vm_manager: Make vma_map private

gl_shader_decompiler: TLDS/TLD4/TLD4S Reworked reflecting the source registers, bugs fixed and modularize.

Based off RE, the backing code only ever seems to use 0-2 as the range
of values 1 being a generic log enable, with 2 indicating logging should
go to the SD card. These are used as a set of flags internally.

Given we only care about receiving the log in general, we can just
always signify that we want logging in general.

Fixes an issue where Testcases couldn't be sent when Telemetry was disabled, because both things are tied closely together in the backend.

service/ldr: Amend layouts of NRO and NRR headers

Amends it with missing values deduced from RE (ProperSystem being from
SwitchBrew for naming)

(SdCardUser wasn't that difficult to discern given it's used alongside
SdCardSystem when creating the save data indexer, based off the usage of
the string "saveDataIxrDbSd" nearby).

hle/service, hle/sm: Minor cleanup

Backport review comment from citra-emu/citra#4418

loaders: Make GetFileType() a const qualified member function

gl_shader_decompiler: TLDS/TLD4/TLD4S Reworked reflecting the source registers, bugs fixed and modularize.

Original reason:
As Windows multi-byte character codec is unspecified while we always assume std::string uses UTF-8 in our code base, this can output gibberish when the string contains non-ASCII characters. ::OutputDebugStringW combined with Common::UTF8ToUTF16W is preferred here.

Mimics hardware behavior.

configuration/config: Use an intermediary variable for accessing players

system_archive: Implement open source NgWord2

Given memory should always be expected to be valid during normal
execution, this should be a debug assertion, rather than a check in
regular builds.

This was only ever public so that code could check whether or not a
handle was valid or not. Instead of exposing the object directly and
allowing external code to potentially mess with the map contents, we
just provide a member function that allows checking whether or not a
handle is valid.

This makes all member variables of the VMManager class private except
for the page table.

 kernel/svc: Correct behavior of svcResetSignal() 

gl_rasterizer: Implement a framebuffer cache

gl_shader_decompiler: Implement TEXS.F16

Combines the two into one, shortening the amount of code here.

Only one usage of the specified objects made use of the lack of
namespacing. Given the low usage, we can just remove these.

These auto-deduce the result based off its arguments, so there's no need
to do that work for the compiler, plus, the function return value itself
already indicates what we're returning.

Gets rid of the need to keep the variables separate from their actual
initialization spots.