Avoid depending on a string match into host_info property, in status output.

[rolandwalker]

Description

Detecting the unix_socket property should be more robust.

Same as #1598 .

Checklist

• I added this contribution to the changelog.md file.
• I added my name to the AUTHORS file (or it's already there).
• To lint and format the code, I ran

  uv run ruff check && uv run ruff format && uv run mypy --install-types .

[github-actions]

1. Correctness regression: TCP connections can be misclassified as Unix-socket connections.
   In mycli/packages/special/dbcommands.py:150, the new condition uses getattr(cur.connection, "unix_socket", None) is not None. In this codebase, TCP paths often pass socket="" (empty string), which is not None, so this branch incorrectly prints UNIX socket and skips TCP port.
   Action: switch to a truthiness check (for example if getattr(cur.connection, "unix_socket", None):) or normalize empty string to None before branching.

2. Missing regression test: no test covers status() with unix_socket="" (TCP connection).
   Action: add a unit test in test/test_dbspecial.py that mocks cur.connection.unix_socket = "" and verifies status() includes TCP port (and not UNIX socket).

No new security concerns identified in this diff.

I couldn’t run tests locally because pytest is not installed in this environment.

[scottnemes]

Verified tcp/socket status output works as expected