Allow device specific properties in profiles

[Ryochan7]

Profiles are considered to be device specific but there is no active way in the code of enforcing that currently. Actions are stored but any mappings mapped to non-existent input groups will be skipped. If there is ever a need for data migration then it might be a good idea to add an identifier in the profile itself to state which controller a profile is made for.

Also, there is the hope to eventually allow more device specific functionality in profiles to allow the use of some functionality available to certain controllers; the main use case would be for allowing more advanced haptic usage with the DualSense controller. Abstracting functionality might not work out as well. Allowing for a mapper and device to handle device specific functionality might be a better route although it would be more work.