strat: update for fsp-ldr 20.0.0 changes

ncm: update to implement new ContentMetaDatabase function for 20.0.0

fusee/exo/ams: update with new keydata/version enums

ams: various fixes to support booting debug configuration

fs: fix uninit warnings on windows localfilesystem

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

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

kern/ldr: add support for --x executables

fusee/exo/ams: update with new keydata/version enums

ams: build with -std=gnu++23

loader: update to reflect latest 18.0.0 changes ...

well, this sure is late, whoops

spl: add support for new spl:es command 33

erpt: actually support non-sequential ids, nintendo why

kern/os: support CreateProcessFlag_EnableAliasRegionExtraSize

fusee/exo/ams: update with new keydata/version enums

fssrv: fix dumb assert error

strat: fix nx_debug build target

loader/ro: abort if patching would go out of bounds

kern/svc: fix query/insecure names

erpt: add remaining SubmitFsInfo helpers

erpt: SubmitFileSystemProxyErrorInfo

erpt: GetMmcErrorInfo, GetSdCard*Info

erpt: begin SubmitFsinfo (SubmitMmcDetailInfo)

jpegdec: fix abort check on output width

jpegdec: update to reflect 17.0.0 changes

pm: adjust resource limit function names

ncm: fix two comments

ncm: better detect + fix 17 brick after-the-fact ...

This adds detection for missing-save or empty-save, and rebuilds in either case.

fs: add missing stub for GetProgramId

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.