feat(linter): eslint-plugin-react checked-requires-onchange-or-readonly

[keita-hino]

partof: #1022

docs: https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/checked-requires-onchange-or-readonly.md
code: https://github.com/jsx-eslint/eslint-plugin-react/blob/master/lib/rules/checked-requires-onchange-or-readonly.js
test: https://github.com/jsx-eslint/eslint-plugin-react/blob/master/tests/lib/rules/checked-requires-onchange-or-readonly.js

[overlookmotel]

@keita-hino In case you're wondering why I have rebased this on main, I made a mistake when converting the benchmarks to run sharded, which lead to benchmarks results not being submitted correctly on some PRs. Now fixed (#2759) so am re-running benchmarks on affected PRs by rebasing on top of the fix.

[codspeed-hq]

CodSpeed Performance Report

Merging #2754 will not alter performance

_{Comparing keita-hino:checked-requires-onchange-or-readonly (5825a98) with main (5080913)}

Summary

✅ 34 untouched benchmarks

[keita-hino]

@overlookmotel Thank you for the fix!

[Dunqing]

Thank you for your work! Let's improve the error message to make it clearer.

[keita-hino]

I'm reconsidering whether performance can be improved.

[Dunqing]

I'm reconsidering whether performance can be improved.

We should try to avoid making memory allocations such as calling to_string

[Dunqing]

I suddenly realized that you don't need to collect prop_names, you just need to iterate through the properties and if you find readOnly or onChange that's the end of it, if not, emit a diagnostic message

[keita-hino]

I have marked the PR as draft to address the performance degradation.

[Dunqing]

The current implementation works well, but it seems we could still improve it by traversing once to find checked, readOnly, onChange and defaultChecked.

[Dunqing]

LGTM, Thanks for the effort you put into improving it!

[keita-hino]

@Dunqing Thank you for your thoughtful review and suggestions for improvement🙏 I've learned a lot!