solid/reactivity should treat functions in mergeProps as being inside a tracking context

[fongandrew]

Describe the bug
If you put a function inside mergeProps that calls a signal or prop, solid/reactivity will warn:

This function should be passed to a tracked scope (like createEffect) or an event handler because it contains reactivity, or else changes will be ignored.

However, this is not true because mergeProps implicitly wraps all functions with a createMemo. You can verify that reactivity still happens here: https://playground.solidjs.com/anonymous/7998ef80-905a-485a-b7d2-9f7f4f4212a6

To Reproduce
Put a function calling a signal inside mergeProps:

const props = mergeProps(props, () => ({ otherProp: signalAccessor() }));

Expected behavior
There is no warning.

Screenshots
https://github.com/user-attachments/assets/a5cad8e7-3e0e-428f-ad1b-2c60435b66a0

Environment (please complete the following information):

• OS: MacOS 15.3.1
• Node version (node --version): 23.5.9
• eslint-plugin-solid version (npm list eslint-plugin-solid/yarn why eslint-plugin-solid): 0.14.4
• eslint version (npm list eslint/yarn why eslint): 9.16.0

Additional context

• I would be willing to contribute a PR to fix this issue (happy to dig in but this issue is also my way of getting a second opinion that functions in mergeProps are, in fact, safe to treat as tracking).

[fongandrew]

FWIW, adding mergeProps to customReactiveFunctions seems to work as a workaround.