Ensure SSL_CERT_DIR messages are always shown and check for existing value

[tomerqodo]

Benchmark PR from agentic-review-benchmarks#3

[sentry]

Bug: The code uses a display path prettyCertDir containing a literal "$HOME" for path comparison. Path.GetFullPath() resolves this incorrectly, causing the check against SSL_CERT_DIR to always fail.
_{Severity: CRITICAL}

Suggested Fix

Use the original full path variable certDir instead of the display-only prettyCertDir when calling Path.GetFullPath() and performing the comparison against the paths in the SSL_CERT_DIR environment variable. The prettyCertDir variable should only be used for logging/display purposes.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/Shared/CertificateGeneration/UnixCertificateManager.cs#L365

Potential issue: The code generates a display-friendly path `prettyCertDir` by
substituting the home directory with the literal string `"$HOME"`. This path is then
passed to `Path.GetFullPath(prettyCertDir)`. Since `Path.GetFullPath()` does not expand
environment variables, it treats `"$HOME"` as a literal relative path, resolving to an
incorrect absolute path like `/current/working/dir/$HOME/...`. This incorrect path is
then compared against the actual paths in the `SSL_CERT_DIR` environment variable. This
comparison always fails when the certificate directory is under the user's home
directory, causing the function to incorrectly report that the certificate is not fully
trusted and prompt users to configure `SSL_CERT_DIR` even when it is already set up
correctly.

_{Did we get this right? 👍 / 👎 to inform future reviews.}