feat: port rule react/checked-requires-onchange-or-readonly

[fansenze]

Summary

Port the react/checked-requires-onchange-or-readonly rule from eslint-plugin-react to rslint.

It enforces that an <input> (or React.createElement('input', ...)) using checked also has onChange or readOnly, and forbids combining checked with defaultChecked.

Achieving full upstream parity required aligning the shared reactutil.IsCreateElementCall detector with eslint-plugin-react's isCreateElement:

• accept optional-chain pragma access (React?.createElement(...));
• reject parenthesized optional chains ((React?.createElement)(...)) and TS-wrapped pragmas ((React as any).createElement(...)), which upstream does not recognize.

These were differential-verified against eslint-plugin-react. The same divergence affected no_unstable_nested_components (which uses the same detector), so its two TS-wrapper test cases were corrected to match upstream.

Related Links

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

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[gemini-code-assist]

Code Review

This pull request implements the new react/checked-requires-onchange-or-readonly rule, which ensures that checked attributes on <input> elements are accompanied by either onChange or readOnly attributes. It also refactors the pragma factory call detection logic in create_element.go to align with ESLint's handling of parenthesized optional chains and TS expression wrappers. The review feedback highlights several critical areas where missing nil checks on AST nodes (resulting from parser recovery on malformed syntax) could lead to nil pointer dereference panics. Code suggestions were provided to safely handle these edge cases.