Ui improvements

see https://github.com/theforeman/staypuft/wiki/UI-Parameters-for-new-wizard
cc @sseago 
**NOT READY**
Well it will *always* fail the first time foreman runs seeds.rb -- this is a bootstrapping sequencing issue -- foreman runs seeds.rb before it loads puppetclasses the first time, and then the staypuft installer runs seeds again. If we fail, then foreman installer will fail (at least this is what happened to me when I first implemented staypuft seeds.rb) Maybe staypuft installer should have some additional step that verifies that certain things happened with regard to seed data? The issue is if the plugin is installed, foreman will run this before puppetclasses are there, so the only way I discovered that worked here was to ignore puppet if it's not ready, and the second run filled in the gaps -- otherwise we have a bootstrapping dep issue like we have (or used to have) with discovery plugin, where having it installed when we first ran foreman installer resulted in failure