fix(auth): Prevent Rare Deadlock Scenario

[tylerjroach]

• PR title and description conform to Pull Request guidelines.

Issue #, if available:
#2816

Description of changes:
If a subsequent auth call is called from within an auth onSuccess/onError callback with runBlocking, it can cause a deadlock. While this is a rare scenario, we can avoid with the changes in PR.

Amplify.Auth.fetchAuthSession( 
  {
    runBlocking {
      AmplifyKt.Auth.fetchAuthSession() 
    } 
  },
  {}
)

How did you test these changes?
(Please add a line here how the changes were tested)

Documentation update required?

• No
• Yes (Please include a PR link for the documentation update)

General Checklist

• Added Unit Tests
• Added Integration Tests
• Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.