feat(gene-tools): allow inline arrow functions calling memoized functions

[RaulVallespinLuque]

Previously, the memoization validator would reject all inline arrow functions in props,
even when they were just passing parameters to a memoized function. This was too strict
and forced developers to create separate variables for simple parameter passing.

This change allows inline arrow functions specifically when they only call a memoized
function, like:
onClick={() => memoizedFn(id)}

where memoizedFn is created with useCallback. This pattern is safe since the called
function is properly memoized, and it improves code readability for simple parameter
passing cases.

Changes:

• Added isCallToMemoizedFunction helper to detect valid cases
• Modified arrow function validation to allow calls to memoized functions
• Added test case and example component to verify the behavior

[Copilot]

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

packages/gene-tools/src/checkers/common/validators/memoizeValidator.js:140

• The current check only supports inline arrow functions with a direct CallExpression body. Consider extending the logic to handle arrow functions with block bodies that return a call expression, if that usage is expected.

if (!isCallToMemoizedFunction(path, path.node.value.expression)) {

[kopach]

probably better to check with authors, but my guess is that original intent was to prevent re-rendering of memoized components. if we pass arrow function as a prop to such component - it will be treated as new reference and component will re-render
Therefore, if my assumption is correct, even though I like this simplification, IMO we can't merge it