feat(lint/noPrototypeBuiltins): add code fix action and cover scenarios from prefer-object-has-own

[kaioduarte]

Summary

Closes #3927

Test Plan

Snapshots + CI

[codspeed-hq]

CodSpeed Performance Report

Merging #3997 will not alter performance

_{Comparing kaioduarte:use-object-has-own (7c37f2e) with main (a3483e4)}

Summary

✅ 97 untouched benchmarks

[Conaclos]

Hi @kaioduarte!

I am sorry, I completely missed the fact that we already [noPrototypeBuiltins](have https://biomejs.dev/linter/rules/no-prototype-builtins/) which has some overlap with the rule you are implementing.
ESLint has both no-prototype-builtins and prefer-object-has-own, but in Biome we try to avoid overlapping.

I think we could improve noPrototypeBuiltins to include the cases that are not yet covered such as Object.prototype.hasOwnProperty.call(). We could also add a code fix as the one you implemented here.
More globally I could even report any read of a prototype builtins (regardless whether it is called or not), e.g const x = Object.prototype.hasOwnProperty.
What do you think?

[kaioduarte]

Sounds good, I'll take a look at that later. Should I add prefer-object-has-own to the rule's sources array?

[Conaclos]

Should I add prefer-object-has-own to the rule's sources array?

Yes. This will avoid thinking that the rule was not covered.

[kaioduarte]

I haven't done the read-only part yet, I only incorporated the changes from the other rule while adapting the code fix.

[Conaclos]

LGTM
Blocking the merging until we decide we no longer ship patch version for Biome 1.9.

I haven't done the read-only part yet, I only incorporated the changes from the other rule while adapting the code fix.

This could be left for another PR.