Fix: respect defaultValue in Select and MultiSelect

[ariser]

Why

Currently, defaultValue in Select and MultiSelect doesn't work. The reason is the effect that tracks updates of the value prop. It runs on mount as well, clearing the state with selected values that should contain default value.

What

• introduced a new hook, useUpdateEffect, that works exactly as componentDidUpdate in classical component lifecycle, i.e. runs every update, but not on the first render
• for tracking value props update, changed useEffect in Select and MultiSelect to useUpdateEffect
• covered the basic behavior of defaultValue with test cases

[vercel]

You must have Developer access to commit code to ClickHouse on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes.

Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles

[ariser]

@vineethasok there are no custom hooks in click-ui as of now, so this is a vital point.
I find both custom hooks, and useUpdateEffect in particular, to be quite useful in certain cases. WDYT? Are you ok with adding a new module with hooks?

I can find other ways to deal with the bug, but in my mind running this effect on updates only is exactly the way to fix it.