This will be used in a following change to svcArbitrateLock() and
svcArbitrateUnlock()

Aligning on 4KB pages isn't a Switch-specific thing, so this can be
moved to common so it can be used with other things as well.

XCI: Add function for checking the existence of the program NCA

Implemented 3D Textures

"Better Hid" Rework Part 1

shader_decompiler: Fix TLDS

Implement flushing in the rasterizer cache

svc: Clarify enum values for AddressSpaceBaseAddr and AddressSpaceSize in svcGetInfo()

Implement Arrays on Tex Instruction

savedata_factory: Add DeviceSaveData and fix TemporaryStorage

Reason for the change is to allow both docked and undocked mode to work

- This will be used as a catch-all for slow-but-accurate GPU emulation paths.

The only reason the getter existed was to check whether or not the
program NCA was null. Instead, we can just provide a function to query
for the existence of it, instead of exposing it entirely.

- This does not really have anything to do with OpenGL.

- These cannot be used within the cache, as they change cache state.

content_archive/patch_manager: Lower log levels to eliminate some unnecessary logs

* Implement VI ConvertScalingMode

* Fixed push enum

* Scale mode now uses Nintendo scale mode as an enum as well

core: Convert shared_ptr instances into unique_ptr instances where applicable for System and Cpu

file_sys/registered_cache: Use unique_ptr and regular pointers instead of shared_ptrs where applicable

Port citra-emu/citra#4327: "travis: Ignore binary files when checking for trailing whitespace"

Required for TemporaryStorage saves (in addition to SaveDataType)

Uses the same path as SaveData except with UID 0. Adds a warning if UID is not 0.

file_sys/registered_cache: Use unique_ptr and regular pointers instead of shared_ptrs where applicable

The data retrieved in these cases are ultimately chiefly owned by either
the RegisteredCache instance itself, or the filesystem factories. Both
these should live throughout the use of their contained data. If they
don't, it should be considered an interface/design issue, and using
shared_ptr instances here would mask that, as the data would always be
prolonged after the main owner's lifetime ended.

This makes the lifetime of the data explicit and makes it harder to
accidentally create cyclic references. It also makes the interface
slightly more flexible than the previous API, as a shared_ptr can be
created from a unique_ptr, but not the other way around, so this allows
for that use-case if it ever becomes necessary in some form.