WPF upgrade

[SadPencil]

Why WPF:

• WinForm has the layout issue which depends on system font and monitor DPI. Not easy to solve (although we can just increase the window size as a workaround).
• MessageBox is not a good tool to display an exception message due to missing scrollbars.
• No need to maintain two windows for gpu message and missing component, respectively. One AdvancedMessageBox is enough.
• No need to be compactible with Wine anymore since Client is .NET 7.

Screenshots:

[SadPencil]

Updated

[Metadorius]

Updated

1. What does this even mean?
   
2. If there's an incompatibility between PC and DX11 version, why is this an option?
   

[SadPencil]

@Metadorius

What does this even mean?

This dialog is launched by the dialog test, because it is hard to reproduce the incompatibility just in order to show the prompt. The only difference is the dialog launched by the dialog test will not do anything and has a (All buttons here won't work) text.

If there's an incompatibility between PC and DX11 version, why is this an option?

This PR only migrates the project from WinForm to WPF. No texts or buttons are changed.
Besides, Alternatively, you can retry launching the DirectX11 version of the client.

[Metadorius]

I recommend to use ReactiveUI.Fody for autogenerating INPC boilerplate.

[SadPencil]

This requires distributing a DLL while the launcher is supposed to be single-file contained

[Metadorius]

LGTM