fix: removed unused react-native-safe-area-context from Dependency

[lalitguy]

Summary

Removed react-native-safe-area-context from dependencies to prevent duplicate native module installations.

Reason

Having this package as a hard dependency can lead to multiple versions of the same native module being installed, which causes build issues in Expo.

Fix

• Removed react-native-safe-area-context from dependencies. (It was not used in the codebase)

Verification

Tested this change by installing the forked branch in an Expo app.
expo-doctor no longer reports duplicate react-native-safe-area-context installations and the calendar renders correctly.

Related issue

Fixes #2728 #2644

[nopitown]

Why is this a dependency (even a peer dependency) if it's not used in the source code? or is it?

[lalitguy]

@nopitown Thanks for pointing it out.
I rechecked the codebase and confirmed that it isn’t actually used.

It was previously listed as a dependency, so I assumed it was required and moved it to peerDependencies. After verifying the usage, I’ve now removed it entirely and updated the MR in the latest commit.

[nopitown]

Thanks @lalitguy, hopefully a maintainer can approve this PR. There are many users waiting for this to be fixed 👀

[twolfvb]

@M-i-k-e-l @nitzanyiz could you guys review this?