ldr/pm: update for 20.0.0 abi changes

strat: update for fsp-ldr 20.0.0 changes

loader: add usb 3.0 enable patches for 20.0.0

Add extensions to dmnt cheat virtual machine (#2479) ...

* dmnt_extension

* update type 8 extension

* clearify that bit 27 does not correspond to a button

* update cheat.md with new code type 0xC4

* implement code type 0xC4

* Add type 1 extension

* remove C0Tcr6Ma aaaaaaaa VVVVVVVV (VVVVVVVV)

* Type 9 extension for floating point math

* updated according to review

strat: ldr::PlatformId -> ncm::ContentMetaPlatform

loader: add usb 3.0 enable patches for 19.0.0

ldr: ProgramInfo is 0x410 now, and fix debug flags for hbl

pm: add new 19.0.0 commands ...

This is functionally correct, but I have no idea what these are meant to represent.
These functions are completely unused on NX.

ns_mitm: update to support new 19.0.0 command

ro: support NROs with read-only first page

kern/ldr: add support for --x executables

kern/strat: update for new DebugFlags capability semantics

kern/creport: use mod0 to locate symbol table for all modules

creport: optimize ScopedFile performance

loader: update to reflect latest 18.0.0 changes ...

well, this sure is late, whoops

loader: add usb3 patches for 18.0.0

spl: add support for new spl:es command 33

dmnt: Fix debug log for cheats

dmnt.gen2: avoid data abort when too many breakpoints are created

dmnt.gen2: enable gdbserver QStartNoAckMode

strat: fix nx_debug build target

pm: improve resource limit management accuracy ...

This change was made for #2255, but the issue creator never confirmed if it resolved the issue.

This *does* better reflect what Nintendo's pm does, though, so I'm going to commit it regardless.

kern: allow ktrace map capability when ktrace is disabled

sm: fix compat with new service macros

pm: update to reflect 17.0.0 internal design changes

pm: since 15.0.0, WaitApplicationMemoryAvailable is more lenient

pm: adjust resource limit function names

loader: add usb3 patches for 17.0.0

ncm: work around change in Nintendo save handling behavior ...

Static save files do not require an entry in the save data indexer to mount.
Prior to 17.0.0, save data files were considered static if userid was 0.
In 17.0.0+, only 8000000000000000 is static.

However, some users using cfw do not have an entry for 8000000000000120 in the indexer,
for various reasons (but mostly manual nand-restore, I think). Thus, on boot of 17.0.0+,
FS will say 8000000000000120 is not present (not in indexer), and NCM will create it anew.

The 8000000000000120 save will then be empty, and then the firmware can't boot.

To workaround this, logic has been re-enabled on 17.0.0+ for building the content meta database.
Thus, if the user encounters this error, the 8000000000000120 save will be emptied, but then
it will be automatically reconstructed, fixing the problem.

bpc.mitm/exo: support pmic reboot/shutdown on mariko (thanks @CTCaer)