fix(auth-info): autoInfo now updates when the authInfo is originally falsy

[ealmeid]

Description

In scenarios where the user starts off as logged out, and attempts to refresh the auth info manually, no changes to the store state will take place because _state.authInfo will already be null and will cause the check to fail.

This particular scenario occurs when leveraging the new ui based hooks. It goes as follows:

1. User is not logged in
2. User logs in successfully using the emailPasswordLogin call from useAuthFrontendApis.
3. The refreshAuthInfo function from useAuthInfo is manually executed
4. user & accessToken remain as null, even though the login flow has completed, and regardless if calls to the /refresh_token endpoint succeeed

Context: This happens because the flow that I'm currently trying to implement involves keeping the user on the root route before redirecting them to a new page, as there is some basic user-related information we'd like to show before redirecting.

I understand this check was originally put in place in this commit, but to compensate for it, optional chaining is put on both the _state & authInfo objects.

[andrew-propelauth]

Thanks for the fix, appreciate it!