Feature: Profiles

[cyberrumor]

This ticket tracks work needed to add profile support.

A profile is a snapshot of a configuration for a particular game. Games may have one or more profiles. The sort of configuration stored by a profile involves which mods are installed/enabled/disabled, which plugins are installed/enabled/disabled, and mod and plugin load order.

Profiles would most easily be added through controller.game, and most easily stored as a folder under ~/.local/share/ammo/<game>/<profile>. Presumably mods for a profile would go under ~/.local/share/ammo/<game>/<profile>/mods.

I think tools should be excluded from profiles. Since they're not installed in the game directory, they're not important to isolate between profiles.

[cyberrumor]

Previously I'd considered making controller.game only show the first game of that particular name in the game selection menu. This would prevent being able to manage the same game installed through multiple avenues (an avenue being json, steam, flatpak) separately.

Since users may already be treating a different avenue like a different profile, we can't limit the menu to only showing the first instance of a discovered name.

[cyberrumor]

In order to prevent users having to migrate their mods, the default profile will store mods in the old location, ~/.local/sahre/ammo/<game>/mods. Profiles could be stored at ~/.local/share/ammo/<game>/profiles/<profile_name> and contain files like ammo.conf and directories like mods.

Creating a profile should happen in the mod controller, not the game controller, because if we want to build a profile by cloning the current profile, we can show users what mods will be copied into the new profile.