Fixes #83818

In some places where debounced inputs where used, we were listening for changes coming from upstream as well using an effect hook. This helps if the same state is changed somewhere else and the input needs to be updated, but it can cause the weird typing issue seen in the original issue, because of this process:
Scenario: User types "abc", waits for 280ms before typing "de", then waits for 280ms again to type "fg"
What they see: "abcde" appearing, flipping back to "abc", "abcfg" appearing, switching to "abcde", then switching back to "abcfg"

• After 256ms the debounce kicks in and pushes the changes to the root
• It takes a while for react to update the whole tree (and it happens async), so the root change reaches the input again after ~300ms
• The user already typed "de", but the root change gets applied, setting the input to "abc"
• The "de" disappears, but it still stored in the debounced callback, and after 256ms "abcde" gets pushed to the root
• In the meantime, the user typed "fg", so the input is set to "abcfg", which is also stored in the debounced callback
• Now, "abcde" arrives from the root update, and the input is set to "abcde" (basically removing "fg")
• After further 256ms, "abcfg" is pushed to the root, and the input changes once again to "abcfg"

Removing the useEffect updating on root state changes fixes this behavior, but introduces a theoretical bug of not reflecting a change somewhere else. However I reviewed the places these inputs are used and we don't have such a case yet. So this is fine for now to fix the bug at hand and we can come back to solve it better once we refactor the state mangement.