Migrate FloatingButton to use new ScreenFooter component internally

[yotam-wix]

Description

• Rewrote FloatingButton component to a function component that renders ScreenFooter internally, while keeping the same external API and visual behavior.
• All existing props work as before, mapped to their ScreenFooter equivalents.
• Added hoisted prop (default: true) that gives FloatingButton built-in keyboard-awareness using screenFooter's logic.
• Updated FloatingButtonScreen to use SafeAreaProvider

Changelog

floatingButton - changed to use new ScreenFooter component internally. deprecated original component.

Additional info

Ticket 5000

[github-actions]

✅ PR Description Validation Passed

All required sections are properly filled out:

• ✅ Description
• ✅ Changelog
• ✅ Additional info

Your PR is good for review! 🚀

---

This validation ensures all sections from the PR template are properly filled.

[yotam-wix]

few things regarding the migration -

1. I've split up the changes to few commits, the first one is the core logic change of the floatingButton component itself and the screen, then there are the tests and api.json file updates.
2. When the footer is used indirectly via floatingButton, it's missing a safeAreaProvider. Perhaps we need to consider wrapping the useSafeAreaInsets inside the screenFooter itself in a try/catch block and let our users know they have to wrap it themselves.
3. Currently, the floatingButton has a bottomMargin prop which controlled the content styling itself. the issue is - footer doesn't have a current support for that, so the component now ignores that prop. some users of us could notice a styling change, and to fix it we could introduce a new contentContainerStyle or bottomMargin prop to screenFooter. WDYT?

[lidord-wix]

• When the footer is used indirectly via floatingButton, it's missing a safeAreaProvider. Perhaps we need to consider wrapping the useSafeAreaInsets inside the screenFooter itself in a try/catch block and let our users know they have to wrap it themselves.

• Regarding the useSafeAreaInsets - it is already wrapped with a try/catch under the optional dependency file, but maybe we can add a warning in the floating button to let the users know that in case they have issues with the safe area they need to wrap it with the provider.. (we have a logService we can use)
• Regarding the bottomMargin - yes, let's add a prop to screenFooter (contentContainerStyle sounds good) and pass the bottom margins there, to make sure the UI will not break for users :)

[lidord-wix]

I added some comments, overall looks good :)
Please make the changelog (in the PR description) more clear 🙏🏽
Also - I wasn't able to run locally, had some issues with the yarn install.. will try again tomorrow

[lidord-wix]

visible is undefined by default in the floating button and true in the screen footer, means that in case the user didn't pass anything and expected it to be invisible, now it will be shown

[lidord-wix]

All the tests are for the hoisted={false} case, let's add some for the default one

[lidord-wix]

let's bring back all the bottomMargin tests to make sure the users aren't break

[lidord-wix]

please format all files before merging the PR (cmd + shift + P -> Format Document) make sure you're doing it with Prettier ESlint (cmd + shift + P -> Format Document With)