max_time_ms_sharded.js uses a fail point to trigger immediate ExceededTimeLimit returns from commands. This triggers during connection establishment via the connection hook, which returns ExceededTimeLimit to the connection pool and causes us to spin on connection creation.

The fix involves checking for ExceededTimeLimit returns and converting them to CommandFailed to avoid the spinning.