Note: the following is pending UI mock-ups from UXD.

Create a new action on content view versions that opens up an incremental update wizard. The wizard should have feature parity with `hammer content-view version incremental-update`. 

The first step, like the publish wizard, can allow users to select the lifecycle environments to publish the new incremental content view version to. The next step can have a content selection for packages, errata and debs (for upstream Foreman). Either on a new step or within the existing steps, there will need to be options for dependency solving, propagating to composite, and updating hosts (see questions below).

Questions:

Should dependency solving be off by default? It is something we want fewer users to use, given the performance and reliability issues.

How should support for --update-all-hosts look? Just a boolean checkbox? Or a show of all hosts that will be updated too, perhaps with a link to customizing the REX job?