Rework profile management

[svartkanin]

I'll throw this in here as an idea and a suggestion at the same time :)

Currently the profile configuration is tightly coupled with the configuration dictionary, which means that it's rather difficult to set/define a profile that can will involve multiple system configurations (e.g. selecting docker server would require the user to be added to the docker group #395)

There's another significant challenge when actually resetting things during the menu configuration, especially when a user will select some profile but then switches to a different one. In that case we have to reset everything that was set previously.

I'd like to rewrite the current profile configuration to something more dynamic and easier to throw around :)
Something along these lines

@dataclass
class Profile:
    def packages(self):   # should return a list of packages
          raise NotImplementedError('Implement me')
          
    def sub_profile(self):   # should return a list of sub profiles (e.g. deskop -> kde
          raise NotImplementedError('Implement me')
          
    def groups(self):   # possible groups the user has to be added for this profile
         return []
          
    ...

This is just a quick example of a possible implementation, but it would allow for better, explicit handling of attributes related to a profile.
Any profile will have to inherit from this base class and implement the relevant methods.

By using actual classes for the profile specifications, we can then also create an API around it to allow users to dynamically create profiles and interact with the existing ones to remove/add packages or functionality

@Torxed any thoughts on this are welcome :)

[svartkanin]

@Torxed would you be okay with me attempting this rewrite for the profiles :)?

I'm happy for any input or suggestions!