feat: add eslint/no-obj-calls

[DonIsaac]

Adds support for no-obj-calls. Provides progress towards completing #479.

[Boshen]

Thank you for the contribution! Only a small change is required.

[DonIsaac]

@Boshen thanks for the review, I'll address your comments. I just updated my PR to support references to global objects, e.g.

// Bad
let a = JSON;
let b = a;
let c = b;
c();
let m = Math
function foo() {
  new m();
}

// Good
let m = Math
function foo() {
  let m = x => x;
  m();
}

I'd appreciate a second look if you can.

[Boshen]

I don't want #510 blocking this PR so I merged it.

Thank you so much for the contribution!

[Maneren]

I know this is already merged and closed but I don't want to open a new issue when it's so recent.

When running the current main branch against the eslint codebase I get the following panic!:

     Running `/home/maneren/.cache/cargo/target/debug/oxc_cli lint /home/maneren/git-repos/eslint/lib/`
thread '<unnamed>' panicked at 'No binding id found, but this IdentifierReference is not a global', crates/oxc_linter/src/rules/eslint/no_obj_calls.rs:94:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Rayon: detected unexpected panic; aborting
[1]    17749 IOT instruction (core dumped)  cargo r --bin oxc_cli -- lint /home/maneren/git-repos/eslint/lib/

That doesn't seem like it's supposed to happen.

[Boshen]

@Maneren Thank you for testing! I'll fix this in #510. And if you interested: #511 😁

[DonIsaac]

@Boshen would you like me to look into this separately or will you cover this in one of your following PRs?

[Boshen]

@Boshen would you like me to look into this separately or will you cover this in one of your following PRs?

A quick removal of that panic would be nice.