feat: add prefer-object-has-own rule

[snitin315]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[x] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add auto fixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Fixes #14939

Resolve #15206

Add a new rule prefer-object-has-own. This rule requires using Object.hasOwn instead of Object.prototype.hasOwnProperty.

Is there anything you'd like reviewers to focus on?

No

[eslint-github-bot]

Hi @snitin315!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

Read more about contributing to ESLint here

[nzakas]

No need to prefix with "[WIP]" (which messes up the commit message check). It's fine to just submit the PR as a draft. That tells us it's not ready for review yet.

[nzakas]

Looks like a good start. The auto fixing is incorrect, I left a comment on one of the invalid tests.

[snitin315]

@mdjermanovic thanks for the review, I have applied the latest feedback.

[mdjermanovic]

LGTM, thanks!

[nzakas]

LGTM. Thanks!

[fisker]

I think the auto-fix will break

return{}.hasOwnProperty.call(object, property)
      ^ no space after `return`.

[snitin315]

Hmm, this should we auto fixed to return Object.hasOwn(object, property) instead of returnObject.hasOwn(object, property).

Thanks, I will fix it in a separate PR.