Include GraphAPI and GraphAPITestMocks targets using SPM

[amy-at-kickstarter]

📲 What

• Add the GraphAPI and GraphAPITestMocks targets to the project as a local swift package, instead of as individual targets.
• Link the Apollo library statically, instead of dynamically
• Link GraphAPI and GraphAPITestMocks statically, instead of dynamically

🤔 Why

• Using SPM means we have fewer targets to configure and manage in XCode. We had some signing issues last release because of how these targets were configured - my hope is that fewer targets = fewer places we can make that kind of mistake.
• Using SPM also means all these files and folders are added automatically, so you no longer have to individually add generated files.
• We link basically all of our dependencies statically and not dynamically, so this is more consistent with the rest of the app.

👀 How

I created a beta distribution build to test this - the build builds and runs!

[nativeksr]

	1 Warning
⚠️	Big PR

Generated by 🚫 Danger

[scottkicks]

LGTM. Excited to see how this impacts!

Just one clarifying change question

[scottkicks]

Why do we need these changes?

[amy-at-kickstarter]

Ah! So it turns out there's a bug with the generator - or maybe with our GraphQL schema. We have two mutations, WatchProjectMutation and UnwatchProjectMutation, both of which return a watchProject object. However, they each return two different types. Every time we re-generate our GraphQL objects, it switches which type it defines, and one of these tests breaks 🤦‍♀️

The tests aren't terrible useful, so one solution would be to delete them. I'm not sure we can fix the backend issue.