fix: Move SearchInput and SideNav callbacks outside of setState.

[skvale]

Description

If the callback with an event is included in the callback of setState the event is not persisted and we lose the event.target
You will see warnings like this:

Warning: This synthetic event is reused for performance reasons. If you're seeing this, you're accessing the property `target` on a released/nullified synthetic event. This is set to null. If you must keep the original synthetic event around, use event.persist(). See https://fb.me/react-event-pooling for more information.
    in SideNav (created by storyFn)
    in provider (created by Provider)
    in div (created by Provider)
    in Provider (created by storyFn)
    in storyFn
    in ErrorBoundary

“Warning: This synthetic event is reused for performance reasons”
This warning is triggered when we try to access to a React synthetic event in an asynchronous way. Because of the reuse, after the event callback has been invoked the synthetic event object will no longer exist so we cannot access its properties.

BREAKING_CHANGE: If consumers had used the SearchInput like the test, where it was expecting the input's ref value to be updated inside of the callback, this is a breaking change, but that seems like a non-react way to handle changes

fixes #629

[netlify]

Deploy preview for fundamental-react ready!

Built with commit af87be0

https://deploy-preview-1165--fundamental-react.netlify.app