fix: replace deprecated SafeAreaView with react-native-safe-area-context to remove deprecation warnings and to ensure future compatibility.

[Harsh-Jaiswal24]

Summary

Replaces the deprecated SafeAreaView from react-native with SafeAreaView from react-native-safe-area-context.
This removes deprecation warnings and ensures compatibility with future React Native versions.

Motivation and Context

React Native's built-in SafeAreaView is deprecated and will be removed in future releases.
Using react-native-safe-area-context provides the recommended replacement and avoids runtime warnings.

Dependencies

• react-native-safe-area-context (already added if not, install via npm/yarn)

Fixes

• Fixes console deprecation warnings related to SafeAreaView

###Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

###How Has This Been Tested

• Ran the example app on iOS and Android to verify the SafeAreaView renders correctly
• Verified no deprecation warnings appear in the console
• Tested navigation and all UI screens using SafeAreaView to ensure layout is consistent

###Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[Harsh-Jaiswal24]

Hello Sir 👋, I’ve submitted this PR to replace the deprecated SafeAreaView with react-native-safe-area-context to remove deprecation warnings and maintain compatibility with future React Native versions.
Please review it when you have a chance. Thank you!

[Harsh-Jaiswal24]

Hi! The workflow failed because forked PRs don't have permission to publish coverage reports (missing write permissions for checks). My code changes are not affected. I'm genuinely interested in contributing here—please let me know if you need anything from me. Thanks!

[azeezat]

Hi! The workflow failed because forked PRs don't have permission to publish coverage reports (missing write permissions for checks). My code changes are not affected. I'm genuinely interested in contributing here—please let me know if you need anything from me. Thanks!

Yes, that is correct. Thanks for creating this pull request!