Update Localized Strings (home-assistant#2090)

Potentially fix invalid authentication issues (home-assistant#2091)

## Summary
There is a potential race condition in token retrieving which could result in providing an old access token to a WebView external auth request. This should at least make it not provide the wrong one, even though the race condition will still occur with the saved keychain data.

## Any other notes
My hunch is that a server's info is updated using stale data just as an access token is updated, which would cause the "grab the server.info.token" to use the wrong access token when constructing the dictionary.

Grabbing it from the server is unnecessary here - we're in the promise chain for getting the new access token anyway, so we can avoid the underlying issue by using the right token when we know it works.

I can sort of reproduce this by hammering server info updates and grabbing the dictionary but not in any way that is reliable enough to write a test around. It may be worth trying to add some sanity checks into the token expirations in the future too. Some additional logging here should make it a little easier to figure out what's going on if/when this reproduces.

Update Localized Strings (home-assistant#2062)

Update Localized Strings (home-assistant#2006)

Update provisioning profiles

Switch to async-less fork of Realm

Bump notification category deprecation to iOS-2022.4 (home-assistant#…

…2004)

Update Localized Strings (home-assistant#1991)

Bump to Xcode 13.2 in CI (home-assistant#1988)

* Bump to Xcode 13.2 in CI

* Swap to non-precompiled Realm/Firebase for now

Update Localized Strings (home-assistant#1979)