When client emits a 40171 error, the underlying auth failure is not exposed to user

[lawrence-forooghian]

When the client emits a 40171 error due to a token error without means to renew token (per RSA4a2), there is no way for the user to find out what was the underlying token error. We should probably be emitting it as the cause of the 40171 error. (Maybe the spec should be tightened to stipulate this, too.)

This will also allow us to update the token revocation tests (to come in #989) to explicitly check for a "token revoked" error, which should be done as part of the current issue.

┆Issue is synchronized with this Jira Task by Unito

[sync-by-unito[bot]]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3760