Bugfix for radix rule and property access

[ajafff]

PR checklist

• Addresses an existing issue: radix lint unintentionally matches any function named parseInt #2281
• New feature, bugfix, or enhancement
  • Includes tests
• Documentation update

Overview of change:

[bugfix] don't warn for missing radix on method calls
[enhancement] added check for global.parseInt and window.parseInt

[andy-hanson]

I wouldn't mark this as fixing #2281 since fixing that would require making this an OptionallyTypedRule.

[ajafff]

You are right, that it does not fix all cases.
I wouldn't make it an OptionallyTypedRule, because it would not fail in CLI but fail in vscode, which is really annoying.

Also other rules like this (no-eval, no-construct, array-type, ...) don't check if the identifier is shadowed. That's what line switches are made for.

If the current behavior is really a problem (awating more feedback on this), we could use some code from no-shadowed-variable (I'm currently working on a reusable utility)