* Fixed conflict with nfp

* Few fixups for nfc

* Conflict 2

* Fixed AttachAvailabilityChangeEvent

* Conflict 3

* Fixed byte padding

* Refactored amiibo to not reside in "System"

* Removed remaining references of nfc from system

* used enum for Nfc GetStateOld

* Added missing newline

* Moved file operations to front end

* Conflict 4

* Amiibos now use structs and added mutexes

* Removed amiibo_path

Everything from here is completely unused and also written with the
notion of supporting 32-bit architecture variants in mind. Given the
Switch itself is on a 64-bit architecture, we won't be supporting 32-bit
architectures. If we need specific allocation functions in the future,
it's likely more worthwhile to new functions for that purpose.

MinGW provides POSIX functions

Used by LovePotion Lua Homebrew. Stubbed as connected to official Nintendo Switch dock.

Updated based off information provided by Switchbrew.

Added based off information provided by Switchbrew.

Updated based off information from Switchbrew

Also introduces the new prepo:a2 service.

Updated based off information provided by Switchbrew.

Updated based off information provided by Switchbrew.

Used by LovePotion Lua Homebrew. Stubbed to return 100% charge.

Seems to be the power controller. Listed in switchbrew under the category PTM services.

This is more localized to what we want to enforce directory-wise with
the project. CMAKE_SOURCE_DIR indicates the root of the source tree, but
this would cause the wrong behavior if someone included yuzu as part of
a larger buildsystem (for whatever reason). Instead, we want to use the
directory where the "project(yuzu)" command was declared as the root
path reference.

CMakeLists: Use target_compile_definitions instead of add_definitions to define YUZU_ENABLE_COMPATIBILITY_REPORTING

Keeps the definition constrained to the yuzu target and prevents
polluting anything else in the same directory (should that ever happen).
It also keeps it consistent with how the USE_DISCORD_PRESENCE definition
is introduced below it.

web_service/CMakeLists: Make the CPPHTTPLIB_OPENSSL_SUPPORT constrained to the web_service library only

Given we link in httplib privately, we can also make the definition
enabling OpenSSL support private as well. Prevents leaking a definition
into other libraries that link with this one, like the core library.

In the kernel, there isn't a singular handle table that everything gets
tossed into or used, rather, each process gets its own handle table that
it uses. This currently isn't an issue for us, since we only execute one
process at the moment, but we may as well get this out of the way so
it's not a headache later on.

These three source files are the only ones within the engines directory
that don't use nested namespaces. We may as well change these over to
keep things consistent.

These are never modified, so we can make that assumption explicit.

This prevents truncation warnings at the lambda's usage sites.

These pointer variables are never used, so we can get rid of them.

This should be comparing against the queried process' vma_map, not the
current process'. The only reason this hasn't become an issue yet is we
currently only handle one process being active at any time.

If the variable being moved is const, then std::move will always perform
a copy (since it can't actually move the data).