Provide a way to track identical controller state updates

In some cases, controllers attempt to update the state but no change is actually made to state. This causes unnecessary re-renders in clients, which can cause performance issues, especially on mobile.

We need a way to track this so that we more information on how to address this issue.

The issue does not name a file, package, entry point, or test. Start by locating the controller state-update paths in the TypeScript monorepo and reviewing how client re-renders are triggered. Done should provide a defined way to identify identical updates and collect information useful for addressing the resulting performance issue.

Written by the indexing model from the issue text.