Add changelog in About window

[yell0wsuit]

Add changelog button in the about window--allow quick looking at the version history (10 most recent) without opening GitHub.

Closes #3262--while in the issue says adding a section for changelog, it would make the about dialog look cluttered. So IMO adding a button to open the changelog window seems better.

[github-actions]

Download the artifacts for this pull request:

• ryujinx-Release-1.1.0+f9a15af-linux_arm64
• ryujinx-Release-1.1.0+f9a15af-linux_x64
• ryujinx-Release-1.1.0+f9a15af-macos_universal
• ryujinx-Release-1.1.0+f9a15af-win_x64

Old GUI (GTK3)

• gtk-ryujinx-Release-1.1.0+f9a15af-linux_arm64
• gtk-ryujinx-Release-1.1.0+f9a15af-linux_x64
• gtk-ryujinx-Release-1.1.0+f9a15af-win_x64

GUI-less (SDL2)

• sdl2-ryujinx-headless-Release-1.1.0+f9a15af-linux_arm64
• sdl2-ryujinx-headless-Release-1.1.0+f9a15af-linux_x64
• sdl2-ryujinx-headless-Release-1.1.0+f9a15af-macos_universal
• sdl2-ryujinx-headless-Release-1.1.0+f9a15af-win_x64

Only for Developers

• ryujinx-Debug-1.1.0+f9a15af-linux_arm64
• sdl2-ryujinx-headless-Debug-1.1.0+f9a15af-linux_arm64
• gtk-ryujinx-Debug-1.1.0+f9a15af-linux_arm64
• ryujinx-Debug-1.1.0+f9a15af-linux_x64
• sdl2-ryujinx-headless-Debug-1.1.0+f9a15af-linux_x64
• gtk-ryujinx-Debug-1.1.0+f9a15af-linux_x64
• ryujinx-Debug-1.1.0+f9a15af-macos_universal
• sdl2-ryujinx-headless-Debug-1.1.0+f9a15af-macos_universal
• ryujinx-Debug-1.1.0+f9a15af-win_x64
• sdl2-ryujinx-headless-Debug-1.1.0+f9a15af-win_x64
• gtk-ryujinx-Debug-1.1.0+f9a15af-win_x64

[gdkchan]

Before implementing something like this, I think we need to automate changelogs. Right now someone has to write it manually after a new version is released, which depends on availability and may take a few minutes, hours or days. That would make the process rather inconsistent as sometimes you would receive the update prompt without a changelog for the latest version.

The second change we need is an easier way to fetch the changelogs, like a json with all the information neatly serialised for the emulator to consume. Using HTML scraping to extract it from the GitHub wiki page is not a good approach.

[Rafacasari]

The second change we need is an easier way to fetch the changelogs, like a json with all the information neatly serialised for the emulator to consume. Using HTML scraping to extract it from the GitHub wiki page is not a good approach.

Maybe using GitHub Tags API to get commits urls and then get the commit message from each tag (like this one)? (ofc it would need some basic regex to remove people e-mail from the message)

And then always make sure to add commit messages properly