Remove seemingly unnecessary ignoring of SIGTERM

[jrafanie]

See the same change in ovirt:
ManageIQ/manageiq-providers-ovirt#80

Replaces #95

It was added originally back in 2011 in manageiq:
946657b11a0a65abbcdca9975206d71f7c2b7afc

This was actually copied from the vmware vim monitoring events
code from 2009: 22a911716b40428b6d822f0f1e95aabd022e59c9

def monitorEvents
  raise "monitorEvents: no block given" if !block_given?

 trap(:TERM) { $log.info "monitorEvents: ignoring SIGTERM" }
...

First of all, trap with logging doesn't work since ruby 2.0+:

irb(main):001:0> require 'logger'
=> true
irb(main):002:0> trap(:TERM) { Logger.new("stdout").info
"EventMonitor#start: ignoring SIGTERM" }
=> "DEFAULT"
irb(main):003:0> `kill #{Process.pid}`
log writing failed. can't be called from trap context
=> ""

See ManageIQ/manageiq#2386

Second, we need to TERM processes in container land.

[miq-bot]

Checked commit jrafanie@d6d3b1c with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. 👍

[moolitayer]

Makes sense. In k8s If we just ignore TERM we will eventually be killed after waiting ~30 sec for no good reason[1]

[1] https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods

[moolitayer]

LGTM 👍

[moolitayer]

@cben @simon3z please review

[jrafanie]

Makes sense. In k8s If we just ignore TERM we will eventually be killed after waiting ~30 sec for no good reason[1]

Yes, this is exactly what @carbonin found, I believe