fatal: Implement Service

[AcK77]

This PR adds a basic implementation of fatal service, guest processes call it when there is something wrong. But since we can already have all informations by debugging it's not really useful. In any case, that's avoid an unimplemented service exception. Structs/Enum are based on Atmosphère source code.

After logs the error report, I call SvcBreak. Feedbacks are welcome on this, since some guests calls it right after fatal service so I can remove it if needed.

(Closes #83 ~finally~)

[github-actions[bot]]

Download the artifacts for this pull request:

• ryujinx-Release-1.1.0+ca31259-linux_x64
• ryujinx-Release-1.1.0+ca31259-osx_x64
• ryujinx-Release-1.1.0+ca31259-win_x64

Experimental GUI (Avalonia)

• ava-ryujinx-Release-1.1.0+ca31259-linux_x64
• ava-ryujinx-Release-1.1.0+ca31259-osx_x64
• ava-ryujinx-Release-1.1.0+ca31259-win_x64

GUI-less (SDL2)

• sdl2-ryujinx-headless-Release-1.1.0+ca31259-linux_x64
• sdl2-ryujinx-headless-Release-1.1.0+ca31259-osx_x64
• sdl2-ryujinx-headless-Release-1.1.0+ca31259-win_x64

Only for Developers

• ava-ryujinx-Debug-1.1.0+ca31259-linux_x64
• ava-ryujinx-Debug-1.1.0+ca31259-osx_x64
• ava-ryujinx-Debug-1.1.0+ca31259-win_x64
• ryujinx-Debug-1.1.0+ca31259-linux_x64
• ryujinx-Debug-1.1.0+ca31259-osx_x64
• ryujinx-Debug-1.1.0+ca31259-win_x64
• sdl2-ryujinx-headless-Debug-1.1.0+ca31259-linux_x64
• sdl2-ryujinx-headless-Debug-1.1.0+ca31259-osx_x64
• sdl2-ryujinx-headless-Debug-1.1.0+ca31259-win_x64

[gdkchan]

Where are the CPU context values supposed to come from? Seems odd that they are all 0s, and some of those CPU registers can only be read by kernel.

[riperiperi]

Code looks OK, but it is weird that the example is passing a cpu context that is all 0s.