[FIX] owl-runtime: don't notify prop signals for alike props

[Gxrvish]

Props returned by useProps are signals, so reading one inside an effect subscribes to it. Until now, every prop signal was updated on each props update, even for the props the template does not compare by identity: .bind and .alike props, and inline arrow functions.

Those props are a new function object on every render, but they mean the same thing, so Owl already ignores them when it decides whether to re-render a child. Reactivity did not. As soon as the child was re-rendered for any other reason, its props object was replaced, the new function went into the signal, and every effect reading that prop ran again.

The compiler now passes the list of those props to createComponent, which stores it on the component node, and useProps skips the signal update when nothing the arrow function captured has changed. A prop signal now notifies in the same cases where Owl decides to re-render.

Note: a .bind prop now keeps the function it already had instead of picking up a newly bound one when the child re-renders for another reason. This is what .alike already means for rendering.

The extra argument is left out when a component has no such prop, so templates compiled with an older compiler behave as before.

Fixes: #2003

[ged-odoo]

hey @Gxrvish i noticed your PR, thanks! I am still thinking about it, not sure if the cost outweigh the value. The useProps function is a function that is called many times, and i want to be careful. but i did not forget this, still not sure, that's it!

[seb-odoo]

Shouldn't the real fix be to use static props for those never changing props?

I might be a little extreme but I'm thinking all props should always be static eventually.

And if their value must change, the static prop should contain a signal/computed to change it through reactivity, not through props change.

I guess the "optimization" might not hurt in the meantime.