Fix sqlserver memory leaking

[XSAM]

Description

Calling ObfuscateSQLStringWithOptions method with an empty optsStr is not the ideal way to use this obfuscate library.

See, https://github.com/DataDog/datadog-agent/blob/928f3f3972c57296ca37e65e344489e2dd407dee/pkg/obfuscate/sql.go#L315-L323

// Ideally we should never fallback to this because it's expensive
log.Warn("falling back to JSON marshalling of SQLConfig options, this should be avoided if possible")

And, this also triggers a memory leak issue in log.Warn from https://pkg.go.dev/github.com/DataDog/datadog-agent/pkg/util/log

Changes

This PR uses the correct and efficient way to call the obfuscate package, and it also resolves the memory leak issue from #42302

Link to tracking issue

Fixes #42302