fix(#3800): MobileSearchAutocomplete: focused style persists on blur

[majornista]

Closes #3800, Closes #3861

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue #3800.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

1. Open https://reactspectrum.blob.core.windows.net/reactspectrum/e6d26f6dcd1b1755c95ac2cd19ceb083d123dbc1/storybook/index.html?path=/story/searchautocomplete--static
2. Open Developer Tools in web browser, and using the Responsive Design tools, select a breakpoint or device width that will render the SearchAutocomplete using the MobileSearchAutocomplete.
3. Verify that using Tab key to set focus to the MobileSearchAutocomplete renders the focus-ring style.
4. Pressing Tab again to blur the MobileSearchAutocomplete should remove the focus-ring style.

🧢 Your Project:

[reidbarber]

LGTM

[LFDanLu]

a bit odd that the order here actually mattered, will dig to see why. Ideally it shouldn't rely on the props merge order

[snowystinger]

funny enough, it's due to this line here https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/interactions/src/useFocus.ts#L78, it should be undefined
the reason the order mattered with it though is due to how mergeProps works with event handler merging, if you pass null as an event handler, it will remove ALL event handlers of that name

https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/utils/src/mergeProps.ts#L45 typeof null is 'object' so we won't go down this path
instead, we'll fall through here https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/utils/src/mergeProps.ts#L66 and overwrite everything

I'm going to push the change to this branch