feat: Add prefer-object-has-own rule.

[Gautam-Arora24]

Fixes #14939

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 autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

This PR focuses on adding a new rule called prefer-object-has-own. The PR adheres to the guidelines provided and has tests and documentation included. This rule requires using Object.hasOwn instead of Object.prototype.hasOwnProperty.

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

Caveats ->
The PR doesn't contain any fixes for the rule.

Fixes #14939

[eslint-github-bot]

Hi @Gautam-Arora24!, thanks for the Pull Request

The first commit message 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 must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

• The first letter of the tag should be in uppercase

Read more about contributing to ESLint here

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Gautam Arora (daf7f3f)

[aladdin-add]

thanks for the PR! I've left a few questions.

[mdjermanovic]

@Gautam-Arora24 you can run npm test locally to see the linting errors and other errors that should be fixed.

https://eslint.org/docs/developer-guide/unit-tests

[Gautam-Arora24]

The latest changes contain ->

• Object-style test cases to assert invalid test cases.
• Reporting to all cases mentioned here.
• All checks successful.
• All changes mentioned above in the review.

[nzakas]

@Gautam-Arora24 are you still working on this?

[Gautam-Arora24]

Sorry @nzakas for the delay. I will create followup commits soon :)

[Gautam-Arora24]

Sorry @nzakas but I am not getting enough time for this PR. If someone wants to pick it up, he/she can feel free to do so :)

[snitin315]

I will fininsh it 👍

[snitin315]

closing in favor of the new PR #15206

[ljharb]

I think you meant #15346

[snitin315]

I think you meant #15346

Definitely 👍