V2.0.* Maintenance Release & Platform Specific Builds

[technosf]

Time to do some maintenance on Tuner and look at the issues that have accumulated.

There are a number of issues related to building or packaging Tuner on platforms other than Ubuntu and Flatpak. Managing numerous build targets could be done within the single meson.build yml file, I assume, yet that is not how I want to proceed. As I do not have access to other platforms to test I want the community to create, test and support specific individual platform build files. I'll speak to this in the open issues where I believe this is the solution. Where should these yml files go? What format should they be named? I'll create an Idea for discussion.

The big bugbear is, of course, light and dark themes. This, again, is hard for me to test as it requires a clean system each time, which I can't do, or access to systems where it doesn't work, which I don't have. However this is not an uncommon issue for various apps: It appears to be the interplay between the assets on the base platform, assets in the package and the requested operation. I've looked at potential ways to create a consistent way to get this to work, such as finding a flatpak Platform that included Adwaita Light and Dark, or figuring out what parts of Adwaita need to be manually dropped into the code base to be there. Both these options would bloat the package size and I have no idea if they would work, or could test such. If you want to try this, please for the Dev repo and try it out.