Improve no-new-array

[fisker]

Currently, when we know the argument is a number, we can auto fix the problem.

But only work for simple cases, we should also smart enough to know cases like new Array(Math.min(unkown1, unknown2)) is calling with a number.

The following are numbers:

• all Math method calls, and Math properties
• Number(unkown)
• Number.parseInt / Number.parseFloat (global parseInt already checked by unicorn/prefer-number-properties)
• BinaryExpressions (-, * , /, %), but NOT + operator, it could be string
• AssignmentOperators (-=, *=, /=, %=)
• unknown ++, unknown --, ++ unknown, -- unknown
• UnaryOperators (+unknown, -unknown, ~unknown)
• Bitwise operators
• Else ?

This will also make other rules like no-new-buffer auto-fix more cases.

[sindresorhus]

This is now accepted.