Move configuration to a single context

[jribbink]

closes #191

Currently, configuration (i.e. that received from FCL via WalletUtils & that derived from query parameters) is not managed as any sort of global state.

It is either passed passed through props OR (in the case of WalletUtils) requested from the client FCL instance in many places as needed.

This presents a few issues for the planned v2 expansion to FCL Discovery (which I have ran into trying to implement these changes)

1. We quickly run into "prop drilling" where variables used by few low-level components are repeatedly passed through parent props (making it difficult to understand where state is coming from)
2. Discovery is continuously sending FCL the "READY" state in order to receive the initialization config in different places throughout the app whenever the useFCL hook is called. Not inherently bad, but shared state would allow us to only query this once and reuse it throughout the app.
3. Without a global context, it's difficult to create SWR hooks throughout the app which rely on this configuration (i.e. a useWallets hook, which is necessary as multiple components need access to this API call). This again necessitates prop drilling and instantiating state at a much higher level in the application than where it is used.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fcl-discovery	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 10, 2024 10:05pm

[chasefleming]

Looks good. Left one comment though.