Pick a default `non-zero` option for `explicit-length-check`

https://github.com/sindresorhus/eslint-plugin-unicorn/blob/f1ced468120686263a45a9993d2f02343f70c6f3/docs/rules/explicit-length-check.md#non-zero-comparisons

I suggest picking a default value for the non-zero option.

not-equal

Pros:

1. !== 0 is the inverse of === 0, like “is it not empty?” and “is it empty?”
2. !== 0 does not perform type coercion (considering that the general consensus is that implicit type coercion is bad)

Cons:

1. If array.length is undefined, array.length !== 0 would evaluate to true, which is incorrect if we are asking “is it not empty?”

greater-than

Pros:

1. If array.length is undefined, array.length > 0 evaluates to false, which is “more correct” than the !== 0 case
2. (subjective) A positive question in a condition is more readable than a negative question, like is it populated? for > 0 vs is it not empty? for !== 0

Cons:

1. Performs type coercion (this actually might be good in this case, see pro # 1)

greater-than-or-equal

Pros:

1. same as for greater-than
2. same as for greater-than

Cons:

1. same as for greater-than
2. (unconfirmed) More mentally demanding because it actually has two conditions in one expression (greater than 1 OR equal to 1)
3. (unconfirmed) Used less often than !== 0 or > 0

I didn’t perform a thorough analysis when I started using !== 0 in my code, and now I think that actually > 0 is a better option.

[sindresorhus]

I agree. I prefer greater-than as default.

[EvgenyOrekhov]

@ryaxc Your example is not polymorphic. There are other types than Array that could have length.