Add recent map and game mode additions

[BitTim]

What is this issue about?

This issue is to house the addition of all recent map and game mode additions

Why now and not when the maps / modes were released?

Honestly, good question. Since I use VexTrack on a regular basis, I just got fed up with setting the map every second game to "None", since it does not exist, as well as having to manually type the name of some modes, since I need to add them as "Custom" games and not even getting result calculation. With the current data structure it literally would be adding a single value, but I already had the opinion that this would be convoluted, to also create and ship a build every time a new map or mode was added and the versioning would not make sense. This is why I also wanted to move to a more hands-off approach, where all data needed would be fetched from an API.

What happened?

The API itself is up and running, since it is a third party API. I wanted to implement data fetching from it and also thought, that since I am already rewriting such a big part of the core, I might also add some improvements / rewrite it from scratch, which is why I started development on v2.0 (#65). As you can tell, that never was released since it was an overly ambitious buggy mess and frankly I did not know what I was doing with Flutter and Firebase. After I let the dust settle a bit and found motivation to try again, I wanted to keep the scope smaller, but alas, I was obsessed with a new design I wanted to implement at the time, that I had made in v2.0, and once again, might as well refactor the entire core. Well, here we are again, the last progress I made with #88 was two years ago and it is still in a less than ideal state. I once again let the project grow out of scope and wanted to add this thing and that thing until it once again grew into a mess and lost motivation. Even now I would like to re-use some parts of it, but since I committed the changes in a messy way, there would be no clean way to do so.

What is the future of VexTrack?

I will probably add this to the README as well but here you go:
VexTrack is an abandoned project of mine, it will not receive active updates (I mean it hasn't got any for 3 and a half years at the time of writing this) and will be replaces by a more recent project, Valolink, which is a more advanced tracker app built primarily for Android. I have some great ideas for that one too, albeit also somewhat ambitious, but I have been steadily chugging along with development. I hope that I can bring Valolink into the state I desire and not abandon it as well, but once again, it's looking good so far.
VexTrack always was and still is a cobbled together mess, it literally started as a simple python script, that evolved up until v1.7, which brought a major rewrite into WPF and C#, that still needed to accomodate some of the mess of the previous versions.

This will be most likely the last update for VexTrack. I will re-introduce a text field to enter a map name manually and update the hard-coded maps and modes. I might do another future update that just updates the maps and modes at a later point in time if Valolink is still not released at that time, but don't count on it. I also might hack in result calculation for custom games if it is a simple implementation.