findCollections and createCollection do not show the correct error message when the Astra token is invalid

[Hazel-Datastax]

When an Astra token is used in the wrong database context, there is an issue with the connection handling. For example, if Token A, which is created for use with Database A, is mistakenly used for Database B, the connection should be refused. However, currently, the connection is established successfully, and it results in an error message Unknown namespace. This is misleading as the real issue is the use of an invalid token for the given database. Therefore, the error message should be changed to Invalid token.

The current error message is:

{
    "errors": [
        {
            "message": "INVALID_ARGUMENT: Unknown namespace 'default_keyspace', you must create it first.",
            "errorCode": "NAMESPACE_DOES_NOT_EXIST"
        }
    ]
}

The error message should be:

{
    "errors": [
        {
            "message": "UNAUTHENTICATED: Invalid token"
        }
    ]
}

[jeffreyscarpenter]

we had to back out the change in #1138, reopening.