Bug in grpcio>=1.54.0

I am getting the following error when I tried to authenticate using username and password.

_**Though using grpcio==1.44.0 solved the issue for now**_

Just created this issue so that others can get an idea about the solutions and this issue gets fixed in upcoming versions.

My etcd database version is 3.5.9 and etcd3==0.12.0

```
Traceback (most recent call last):
File "", line 1, in
File "/root/myproject/venv/lib/python3.10/site-packages/etcd3/client.py", line 48, in handler
_translate_exception(exc)
File "/root/myproject/venv/lib/python3.10/site-packages/etcd3/client.py", line 46, in handler
return f(*args, **kwargs)
File "/root/myproject/venv/lib/python3.10/site-packages/etcd3/client.py", line 534, in status
status_response = self.maintenancestub.Status(
File "/root/myproject/venv/lib/python3.10/site-packages/grpc/_channel.py", line 1030, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/root/myproject/venv/lib/python3.10/site-packages/grpc/_channel.py", line 910, in _end_unary_response_blocking
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAUTHENTICATED
details = "Established channel does not have a sufficient security level to transfer call credential."
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"Established channel does not have a sufficient security level to transfer call credential.", grpc_status:16, created_time:"2023-06-25T10:18:55.858860189+00:00"}"
```

Start by reproducing username/password authentication with etcd 3.5.9, etcd3==0.12.0, and grpcio>=1.54.0. Inspect etcd3/client.py around status and authentication, then compare the behavior with grpcio==1.44.0. Done means identifying the compatibility issue and confirming a fix or documented supported-version path.

Written by the indexing model from the issue text.