fix: addressed an issue where connection strings for databases such as PostgreSQL were wrongly identified as Redis connections

[nithinputhenveettil]

This PR addresses two issues related to the auto-detection of database names from connection strings:

1. Incorrect Identification of PostgreSQL Connections as Redis Connections

The issue arose because the regex used for detecting Redis connections was too generic and did not handle all edge cases. Specifically, it failed when the password was optional in certain connection strings. The regex has been updated to be more specific, with added handling for these edge cases. The new regex now correctly handles the following components of a URI:

• The URI scheme (optional)
• The username (optional)
• The optional password (if present, separated by a colon)
• The hostname
• The port number

With this modification, Redis connections are now correctly identified, and PostgreSQL URIs are no longer incorrectly flagged. Additionally, new unit tests have been added to cover these changes.

2. Incorrect Database Name Identification for PostgreSQL URIs

The logic previously only recognized the URI scheme postgres for PostgreSQL, which caused issues when the postgresql scheme was used. According to the official PostgreSQL doc, both postgres and postgresql are valid URI schemes. The logic has been updated to correctly handle both schemes and identify the database name accurately in all cases.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud