Disable the NumericPredicate cop

[ygnessin]

https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Style/NumericPredicate

This cop does not support auto-correct, is generally noisy in our codebases,
and not that helpful. Reasoning for the default is dubious:

"The default is the predicate. The benefit of that is you'll avoid silent
errors when accidentally comparing to nil, and will instead get a runtime
error. The downside is people might not immediately know whether 0 is
considered positive or not."

• positive? vs >0 cops rubocop/rubocop#5564 (comment)

I'm not sure about that reasoning because nil > 0 is not a silent error.
Also, the conditional style is more performance (on a micro scale)

[ygnessin]

Ah, after posting this I figured out what it's talking about:

2.6.1 :009 > nil == 0
 => false 
2.6.1 :010 > nil.zero?
Traceback (most recent call last):
        4: from /Users/yuval/.rvm/rubies/ruby-2.6.1/bin/irb:23:in `<main>'
        3: from /Users/yuval/.rvm/rubies/ruby-2.6.1/bin/irb:23:in `load'
        2: from /Users/yuval/.rvm/rubies/ruby-2.6.1/lib/ruby/gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        1: from (irb):10
NoMethodError (undefined method `zero?' for nil:NilClass)

If the rest of the team thinks this difference is meaningful then I could understand wanting to keep this cop. However, it is scary to think that converting x == 0 to x.zero? is a functional change and may introduce bugs if we "just do it"; that's probably why the cop doesn't support autocorrect.