Change package.json for React Native to allow for optional deps for views

[bjtrounson]

This is a small PR and related to #425

I've been wondering about a way to properly do this within the package.json and was looking through some other projects and found the way https://github.com/computerjazz/react-native-draggable-flatlist/blob/main/package.json handles this.

It seems peerDependencies seems the way to go, look through the documentation on NPM and it seems we can label some of the peer deps as optional which I think will work well for the view related packages (React Native MapLibre and so on.)

Documentation if anyone else want to have a look in case I've missed something https://docs.npmjs.com/cli/v11/configuring-npm/package-json#peerdependencies

This PR just makes that change. Another way to potential do this is to separate the view and core logic into to two separate package which we upload separately onto NPM

[ianthetechie]

This makes sense to me! Seems like a reasonable first step at least.

I haven't had much chance to think through the npm packaging of the React Native module yet, but this is an interesting idea, since you can explicitly denote optional dependencies.

I think the main argument for separating the packages is that users wouldn't need to download code which they won't use. Is that worth the overhead of maintaining multiple npm projects in the workspace? I'm actually not sure, but it does seem to make things significantly more annoying to work with.