License Dialog should be configurable

[ruspl-afed]

Although it is obvious for Passage to reduce the list of troubles with both agreements and features to the only bit of information "can use" - for user it may be not so helpful to see them in one generic table.

The suggestion is to redesign access to License Dialog to let product decide how to represent it better

[zelenyhleb]

@ruspl-afed IMO, from UX point-of-view, the best will be including suggested actions to each row of License Dialog table like on screenshot below.

By making actions contextual we improve dialog "passability" a lot, because in this case people can guess, what do we expect from them. It becomes like a "wizard", where you need to pass some steps before dialog lets you in.

WDYT?

[ruspl-afed]

I'm fine with [additional] contextual actions, my point is to avoid generic table where things with different origin are mixed.

I would prefer 2 tables, like

1. "License Agreements to Accept"
2. "Features to cover with License"

[ruspl-afed]

@zelenyhleb you are right, there may be a lot of ways to implement this, let's better do it configurable