Create <WordPressProvider /> Component to House Context

[gregrickaby]

I feel like global-y things like Menus, Settings, SEO, etc... should be managed in a new <WordpressProvider /> component, rather than passed down by every query.

• [x] Create <WordPressProvider /> component (it should follow this pattern)
• [x] The Provider should have a useWordPress() hook
• [x] Add new provider to _app.tsx
• [x] Create a query for global items like menus, settings, and SEO
• [x] Place query results into state
• [x] Use the useWordPress() hook to grab the state and pass into other components like, <Layout />

[gregrickaby]

Because I removed Tailwind, I might as well spin up a provider as part of #26. Less to juggle!

[leonlafa]

I feel like global-y things like Menus, Settings, SEO, etc... should be managed in a new <WordpressProvider /> component, rather than passed down by every query.

Yeah, I agree, this would be a better solution.