chore: Autofix n.26

[AndreaBozzo]

Automated hotfix.

In general, to fix cleartext logging of sensitive information, you should avoid including sensitive fields (like passwords, API keys, tokens) in any object that can be implicitly logged with Debug/Display, or ensure they are redacted before logging (e.g., replaced with "***" or omitted). In Rust, a common fix is either to remove Debug for the sensitive type or to provide a manual Debug implementation that redacts sensitive fields, while leaving program behavior otherwise unchanged.

For this code, the minimal change that avoids leaking password in logs without altering functionality is:

• Remove the #[derive(Debug)] from ConnectionInfo, since it currently includes the password field verbatim.
• Add a manual impl std::fmt::Debug for ConnectionInfo that prints all non-sensitive fields as before, but redacts the password field (e.g., always printing Some("REDACTED") when a password is present, or None otherwise). The stored password value remains unchanged and is still available to the rest of the program.

Concretely:

• In src/database/connection.rs, change the #[derive(Debug, Clone)] on ConnectionInfo to #[derive(Clone)].
• Immediately after the ConnectionInfo definition, add a manual impl std::fmt::Debug for ConnectionInfo that formats the struct, but replaces the actual password with a placeholder. No new external dependencies are required, only std::fmt from the standard library (fully qualified).

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[AndreaBozzo]

This alert was autotriggered, odds of this happening were ultra low as we don't derive db structures right now.
Still, taking no chances and extending it a bit