Move example Settings.bundle outside of this Xcode project

[friedbunny]

We include an example Settings.bundle with a localized opt-out for Mapbox Telemetry (#2380). However, Xcode has never liked how we build this file and keeps throwing new warnings at us (#6948, #7698). In Xcode 8, 9, and 10b5, this is the warning we see:

Check dependencies

Warning: The Copy Bundle Resources build phase contains this target's Info.plist file 'framework/Settings.bundle/Root.plist’.

As our example Settings.bundle doesn’t appear to be well-used in its current iteration (few customer apps include this setting and, of the ones that do, I couldn’t find any that include the localized text), we should consider moving it to the ios-sdk-examples repo/project. This would remove the persistent warning and place it in more natural location (i.e., alongside other examples).

/cc @1ec5 @captainbarbosa

[friedbunny]

Various public docs around this repo (and Mapbox generally) refer to this Settings.bundle, so those will also need to be audited.

There may also be localization scripts/keys to remove.

[1ec5]

Rather than removing the bundle outright, as in #12607, why not make it an ordinary resource in iosapp? That would resolve all the warnings, and it can benefit from translations from Transifex and iosapp gets a Settings bundle. We can still copy the bundle into the example project if that makes it more discoverable.

In theory, we could also automatically include the Settings bundle into an application if it’s installed via CocoaPods, along the lines of #3160, but that might be too aggressive.