Allowed components to be focused with "setFocus" even if they have "focusable=false"

Latest feature with focusable prop had a check inside setFocus function that blocked component from being imperatively focused. This caused certain regressions, for example when you "setFocus()" on the whole page on mount. The previous logic allowed to save target focus key even if component doesn't exist yet, and then when it gets mounted, the focus was set to this component. So this check was removed to allow setting focus manually on any focusKey (even non existent ones) with setFocus.
Assuming you have full control of where you call setFocus, you can avoid setting it to components that should have focusable={false}, which you also have control of.
focusable prop now only affects "automatic" navigation logic such as directional navigation, focusing lastFocusedChild or preferredFocusChild.