[8.18](backport #45857) [metricbeat] [sql] sanitizeError: replace sensitive info even if it is escaped, add pattern-based sanitization

[mergify]

Suggested fix for the connection string leak described in the issue: #45852

After this change not only sensitive string will be replaced in the error message, but the escaped and url-encoded representations of it will be replaced. (Escaped as in fmt.Sprintf("%q", sensitive)). Additionally, this PR also improves sanitizeError by adding pattern-based sanitization.

What triggered the original issue: net/url library (in case of the issue, invoked by mssql driver) has its own error type which uses %q when printing URLs:

// go/src/net/url/url.go
type Error struct {
	Op  string
	URL string
	Err error
}

func (e *Error) Error() string { return fmt.Sprintf("%s %q: %s", e.Op, e.URL, e.Err) }

Additional refactoring:

• moved SanitizeError to the "github.com/elastic/beats/v7/metricbeat/helper/sql" package as it is a generic helper function, which is also related targeted at errors returned by sql driver libs
• implemented custom error type sqlSanitizedError so that errors.Is() and errors.As() still work with the errors returned by SanitizeError
• adding error checks or //nolint:errcheck comments in "github.com/elastic/beats/v7/metricbeat/helper/sql" package, as changes there triggered more CI checks

Proposed commit message

See title.

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.

How to test this PR locally

1. Use metricbeat module sql with driver set to driver: mssql
2. Set hosts to some invalid string with symbols (", \, etc.)
3. The parse error shouldn't contain the host connection string, but contain (redacted) in the place of it

Related issues

• Closes [Metricbeat] [SQL] connection string leaking to error logs when failed to parse #45852
• Relates [Metricbeat] [SQL] Remove connection string from error message #44577

---

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

[mergify]

Cherry-pick of bf63860 has failed:

On branch mergify/bp/8.18/pr-45857
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit bf63860f1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.next.asciidoc
	modified:   metricbeat/helper/sql/sql.go
	modified:   metricbeat/helper/sql/sql_test.go
	modified:   x-pack/metricbeat/module/sql/query/query.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   x-pack/metricbeat/module/sql/query/dsn.go
	deleted by them: x-pack/metricbeat/module/sql/query/query_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mykola-elastic]

Manual testing - PASS