Use ruby not runner for run single worker

[jrafanie]

This is another version of #15821

Basically:

• drop ui_dependencies from the manageiq_default gemset
• use this gemset for all non-ui workers
• add ui_dependencies for ui_workers and non worker rails processes (runner, console, etc.)
• Change Procfile example to use ruby not bundle exec rails runner

This is a way to dial back the aggressive "minimal" gemset selection for best benefits with much less risk.

We can continue to try to find solutions to the problems described here and try to whittle away/decouple the dependencies.

The concern is any worker could try to constantize a constant in a gemset such as below. We need a better story for how to deal with that.

[----] I, [2017-08-16T14:15:02.432484 #39682:3fe16d83fa0c]  INFO -- : MIQ(MiqQueue.get) Message id: [1000000001483], MiqServer id: [1000000000001], Zone: [default], Role: [], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqEvent.raise_evm_event], Timeout: [600], Priority: [100], State: [dequeue], Deliver On: [], Data: [], Args: [["ManageIQ::Providers::Vmware::InfraManager", 1000000000004], "ems_auth_unreachable", {}], Dequeued in: [392.403107] seconds

[----] E, [2017-08-16T14:15:02.952992 #39682:3fe16d83fa0c] ERROR -- : [NameError]: uninitialized constant ManageIQ::Providers::Vmware  Method:[block in method_missing]
[----] E, [2017-08-16T14:15:02.953031 #39682:3fe16d83fa0c] ERROR -- : /Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/inflector/methods.rb:270:in `const_get'
/Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/inflector/methods.rb:270:in `block in constantize'
/Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/inflector/methods.rb:266:in `each'
/Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/inflector/methods.rb:266:in `inject'
/Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/inflector/methods.rb:266:in `constantize'
/Users/joerafaniello/.gem/ruby/2.3.4/gems/activesupport-5.0.5/lib/active_support/core_ext/string/inflections.rb:66:in `constantize'
/Users/joerafaniello/Code/manageiq/app/models/miq_event.rb:30:in `raise_evm_event'
/Users/joerafaniello/Code/manageiq/app/models/miq_queue.rb:387:in `block in deliver'
/Users/joerafaniello/.rubies/ruby-2.3.4/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/Users/joerafaniello/.rubies/ruby-2.3.4/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/Users/joerafaniello/.rubies/ruby-2.3.4/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/Users/joerafaniello/.rubies/ruby-2.3.4/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/Users/joerafaniello/.rubies/ruby-2.3.4/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/Users/joerafaniello/Code/manageiq/app/models/miq_queue.rb:386:in `deliver'

[miq-bot]

Checked commits jrafanie/manageiq@c57b0b7~...cb63b4b with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
3 files checked, 0 offenses detected
Everything looks fine. ⭐

[NickLaMuro]

tl; dr; 👍

I like this approach, and much prefer it to my "fix the two things that were bothering me at the time" PR, #15821

While I this will bloat what we have a bit, it won't be so bad because we autoload everything (for better or worse). I think the stability benefits we gain from this and actually launching things in foreman the way I had intended (and doing this before this becomes a heavily used standard for developers) far out way the loss memory locally for now.

That said, we should get a plan in place to start tackling striping this down, but that can be done later.

[NickLaMuro]

@carbonin @gtanzillo When you have time, I think me and Joe have agreed that this is the path we would like to start on for a reset on getting the bundler groups working properly, and having this in place is needed for that.

To avoid a 📖 , I will leave it at that, but let me know if there is anything that is confusing about this approach.

[carbonin]

Looks good

[gtanzillo]

Looks good to me 👍