Render a full requirements tree of the profiles

[kMutagene]

While it is nice that we managed to re-use and extend existing workflow/run profiles, getting a full picture of the profile is near impossible as the dependencies are at no point resolved, meaning that information about requirements from profiles we base ours on are hidden on those profile descriptions. The nesting goes down even further, as dependencies are not resolved on those as well.

I get the reason why it is easier to point to an external thing, but for the sake of understanding our own profiles (and keep our sanity), we should resolve all profile dependencies in our profile descriptions.

[kMutagene]

See also #5