[9.0](backport #44577) [Metricbeat] [SQL] Remove connection string from error message

[mergify]

Proposed commit message

See title.

Use cases

This PR handles specifically the case when the mssql driver is used and the port number supplied is wrong, for example, 4xf. In this case the underlying library exposes the password (the whole connection string) in the error message and we get something like this in the logs:

[elastic_agent][warn] Unit state changed sql/metrics-default-sql/metrics-sql-1ff7729a-ac72-45c3-a643-dbd3bc24f4aa (HEALTHY->DEGRADED): Error fetching data for metricset sql.query: cannot open connection: testing connection: parse "sqlserver://SA:1234_asdf@host.docker.internal:4xf": invalid port ":4xf" after host

After this fix the string gets replaced by (redacted), like this:

[elastic_agent][warn] Unit state changed sql/metrics-default-sql/metrics-sql-1ff7729a-ac72-45c3-a643-dbd3bc24f4aa (HEALTHY->DEGRADED): Error fetching data for metricset sql.query: cannot open connection: testing connection: parse "(redacted)": invalid port ":4xf" after host

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Related issues

• Relates https://github.com/elastic/obs-integration-team/issues/304

---

This is an automatic backport of pull request #44577 done by [Mergify](https://mergify.com).