Fix settings sanitization immutability issue

Since Object assignment in Javascript is by reference and not by value,
the `sanitiziedSettings` initialization in both sanitiziation functions
would actually modify the `defaultSettings` which should be immutable.

This commit fixes this issue by initializing `sanitizedSettings` with
the object spread operator so to not create a reference but create a new
object instead.

Author: matei-radu

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@matt-block/react-native-in-app-browser",
-  "version": "1.1.0-rc.1",
+  "version": "1.1.0",
   "description": "React Native in-app browser",
   "keywords": [
     "in-app",
@@ -75,4 +75,4 @@
       "git add"
     ]
   }
-}
+}

src/settings.ts

@@ -182,7 +182,7 @@ export function sanitize(os: PlatformOSType, settings?: Settings) {
 }
 
 function sanitizeAndroid(settings?: SettingsAndroid): SettingsAndroid {
-  const sanitizedSettings = defaultSettings.android!;
+  const sanitizedSettings = { ...defaultSettings.android! };
 
   if (!settings) {
     return sanitizedSettings;
@@ -222,7 +222,7 @@ function sanitizeAndroid(settings?: SettingsAndroid): SettingsAndroid {
 }
 
 function sanitizeIOS(settings?: SettingsIOS): SettingsIOS {
-  const sanitizedSettings = defaultSettings.ios!;
+  const sanitizedSettings = { ...defaultSettings.ios! };
 
   if (!settings) {
     return sanitizedSettings;