[FEATURE] Indication of the type of capture (amp, full rig etc.) in the NAM plugin gui

[IsaakCode]

Is your feature request related to a problem? Please describe.
I have various profiles downloaded from ToneHunt and other reposities saved to a directory. There is no indication whether the profile covers the amp only or the full-rig when I load it into NAM. There is also typically no clear indication in the file name of the profile, the info is only available in the repository.

Describe the solution you'd like
A visual indicator / text field in the NAM gui giving away the type of profile (amp, full rig, outboard device, pedal). This probably requires that the profile file contains that info. Maybe in the NAM Trainer an obligatory selection can be added to indicate the type of profile, with that info made visible in the NAM plugin?

This could also be used further down the line for a preset browser, that allows selection of profiles in the user library according to type.

Alternative
Connect NAM plugin with the ToneHunt repository via an included file browser that retrieves and displays the profile type from the ToneHunt database and which allows downloads of profiles directly from within NAM plugin to a specified user directory.

[sdatkinson]

TL,DR:

• Some models do have the metadata to do this, but it's not mandatory to provide and I won't make it so.
• I'm open to implementing this into the plugin.

Metadata is currently optional and easy to provide using e.g. the Colab trainer:

As well as the GUI trainer:

I could imagine something like one of several icons lighting up in the plugin based on what kind of model the file is annotated as in its metadata (or a question mark if it's not provided).

To do this, I'd need some image artifacts with enabled/disabled versions similar to the amp and IR icons (e.g. IRIconOn.svg / IRIconOff.svg). Probably a pedal, amp, cab, preamp(?), and studio(?).

Putting this all on the left side where ModelIcon.svg lives currently makes sense to me, but I'm open to suggestions.

[38github]

It would be "cool" if the IR is inactivated when a full_rig is loaded and activated when a non full_rig is loaded. It would be a good idea to have an option to disable that behaviour though.