V6 rebuild project

[robinmacharg]

Goal

Previous work to combine three separate Xcode projects didn't go far enough and left a folder structure that didn't follow Apple best-practice and, further, wasn't amenable to consistent install instructions. This work rebuilds the entire project structure to address these issues.

Design

• A new Xcode iOS framework project was created.
• Framework targets for each platform were added, along with tests and a static target.
• Build settings from the previous project merge were copied across
• Source files were moved from existing locations to preserve history, with additional directory structure added. Tests were also re-added. A single redundant Swift test was elided.

Commits were granular and show the progression towards a stable state. Pushes were frequent to ensure that CI issues were addressed. Builds were attempted frequently locally. Popular open source frameworks were consulted to ensure best (common) practice was followed as much as possible.

Changeset

• Project file added at top level, source files moved; this generates a large changeset that may be better reviewed as a checkout. v6 changes were merged in to ensure that the two branches did not diverge too greatly.
• Makefile adjusted for new source path

Tests

Manual install, Cocoapods, Carthage both local and remote.

[fractalwrench]

Noticed a few things that differ compared to the previous project that I believe need to change:

• The Link Binary with Libraries step appears to be missing the frameworks from the previous project
• The BugsnagStatic target is missing a copy headers build phase, which means headers will not be available for React Native
• The BugsnagStatic target is missing around half the required .m files from the Compile Sources Build phase
• The test targets have an inconsistent number of files in their build phase

I've tested this by confirming that it works in the Obj-C example project - we would need to test against all our installation instructions before merging this.

[fractalwrench]

Updated PR to address the review points raised above - I've tested out on an example app using Cocoapods only. @tomlongridge would be good to get another pair of eyes reviewing this.

[tomlongridge]

Do we need Configurations/Config.xcconfig any more? I believe this was used to share config across projects (but was causing the manual install instructions to break), so I believe it is now unused.

[fractalwrench]

Configurations/Config.xcconfig does not appear to be necessary - I've deleted this and rebased the PR to resolve conflicts from the deadlock fix merged into v6.