CosmosClient with invalid key throws DocumentClientException when ReadAccountAsync called

[andrewdmoreno]

Describe the bug
DocumentClientException is thrown when CosmosClient is instantiated with an invalid key (I.E. key was since rotated) and ReadAccountAsync called.

Seems to be related to #1906.

To Reproduce

        [TestMethod]
        public async Task EnsureUnauthorized_ThrowsCosmosClientException()
        {
            var authKey = ConfigurationManager.AppSettings["MasterKey"];
            var endpoint = ConfigurationManager.AppSettings["GatewayEndpoint"];

            var cosmosClient = new CosmosClient(endpoint, authKey);

            var exception = await Assert.ThrowsExceptionAsync<CosmosException>(() => cosmosClient.ReadAccountAsync());
            Assert.AreEqual(HttpStatusCode.Unauthorized, exception.StatusCode);
        }

Expected behavior
CosmosException should be thrown with status code 401.

Actual behavior

Assert.ThrowsException failed. Threw exception DocumentClientException, but exception CosmosException was expected. 
Exception Message: The input authorization token can't serve the request. Please check that the expected payload is built as per the protocol, and check the key being used. Server used the following payload to sign: 'get

Environment summary
SDK Version: Microsoft.Azure.Cosmos 3.20.1
OS Version: Windows

[ealsur]

Closed by #2792

[j82w]

Please try the latest 3.22.0 SDK which has the fix