User is told localhost connection is failing for database connect, not database is unavailable

[stevenGravy]

Expected behavior:

A user would be told the database is not available, not that localhost connections failed.

Current behavior:

A user gets generic errors about localhost on their machine. The problem is the database connection attempt failed from the database service. To the user it looks like the failure is on connecting to their localhost.

$ tsh db connect --db-user=postgres --db-name=xyz example2
psql: error: connection to server at "localhost" (::1), port 63531 failed: Connection refused
	Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (127.0.0.1), port 63531 failed: failed to handle client connection
ERROR: exit status 2

Bug details:

• Teleport version: 17.0.5
• Recreation steps

1. Add a database service such as a postgres
2. Have the database be unavailable
3. Attempt to connect via tsh db connect