Failure to fetch ConnectionToken on app init does not throw or surface error

[stripe]

Failure to fetch ConnectionToken on app init does not throw or surface error

[jdivock-stripe]

Also of note that the invalid connection token appears to be cached, we should reset it internally when it fails so a new one can be fetched

[jdivock-stripe]

going to raise the priority on this one as it's a pretty frustrating failure mode. The SDK will continue to try to perform actions and often just silently fail if it cannot reach the backend or has an invalid connection token.

[jdivock-stripe]

I worry fundamentally about having fetchConnectionToken fire on app mount a this seems fairly unexpected and I'm unsure how we'd properly wire in error surfacing around this. Can we refactor the SDK to be explicitly initialized by the user so they can delay configuring it without having to guard against mounting anything nested in <StripeTerminal/>

cc @dhenry-stripe