Handle missing react-native-safe-area-context in ScreenFooter screen

[adids1221]

Description

Fixes crash in ScreenFooterScreen demo when react-native-safe-area-context is not installed.
Replaced the direct import with a try/catch require and added a fallback screen with install instructions.
Fixed a circular import in ScreenFooter (import {Image} from 'react-native-ui-lib' → import Image from '../image') that broke the barrel export when the optional dependency was missing.

Changelog

ScreenFooterScreen - Gracefully handle missing react-native-safe-area-context dependency.

Additional info

N/A

[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.

[M-i-k-e-l]

It does solve the require issue, however when the screen is selected and react-native-safe-area-context is not installed there is a red screen

[M-i-k-e-l]

The first fix (about the Image) is a good find!
However the second one is removing usages of ui-lib which seems like a bad fix even if it works.
Let's revert the second commit and merge, I might have a solution for the rest.

[adids1221]

Reverted.
The reason for using RN primitives was that uilib's View uses useSafeArea which also depends on react-native-safe-area-context, so the fallback screen would crash too. But happy to go with your solution!