[android] make sure devicePushToken AsyncCondition is always resolved properly

[esamelson]

Why

Fix for #2381 . It's currently possible to get in a state where the AsyncCondition for devicePushToken is resolved before the conditions in isReady in the method to get the Expo push token are met. In this case, the promise from the getExpoPushTokenAsync method never gets resolved or rejected.

How

Changed the isReady condition and the location of the AsyncCondition.notify calls so this state is no longer possible.

Also ensured that even if errors happen in the body of the onHandleIntent method, AsyncCondition.notify will still be called => the promise will be rejected instead of hanging.

Test Plan

Built a standalone app that logs the Expo push token immediately upon launch. Before this change, the promise would never resolve ~75% of the time on a fresh install. After the change, it has resolved 10/10 times I tested.

[ide]

This looks better than before but I think the behavior is still suboptimal in that the first boot still requires the updatePushToken request to succeed (not a regression, just that we'll still want to revisit this during the SDK audit).

[esamelson]

ok, that makes sense. I think this fixes the main cause of #2381, however, so I'm going to merge this now so we can get it into a bugfix turtle release ASAP.