Automatically set change detection for traits that are being observed

[krispya]

Right now change detection is set per updateEach call manually, default off. The proposal is to make change detection be on, off, or auto instead of a boolean, with default being auto. If auto then it would follow these rules:

• All traits that are observed for changes with onChange are added to a tracking list.
• If a query result selects for a tracked trait then it automatically enables change detection for that trait only.
• If the trait is no longer observed, this is automatically switched off.
• This can be overwritten by setting auto to off.

There was suggestion to make this even more specific, per entity per trait. There is no API for that currently (you can observe all entities for a given trait, not specific entities, and then filter for specific entities) so this should be opened as another issue.

[Ctrlmonster]

Looks good. Yeah I think entity + trait can be an implementation detail eventually. Since the public listening API requires you to pass an Entity in all cases anyway (unless I'm missing some?). Storing the tuple (trait, entity) in the tracking list should greatly reduce the number of comparisons and thus improve perf, making auto a save option in basically all cases. But since this issue is about the updateEach API, I think it's good as it is 👍

[krispya]

Only the React API makes you pass in an entity. The core API does not (onChange) and neither does tracking queries using the Changed modifier.

[Ctrlmonster]

I see. Okay let's put that discussion in another issue, since this is pretty much agreed on.