[dbm] add keep_json_path to obfuscator_options

[lu-zhengda]

What does this PR do?

This PR adds keep_json_path to obfuscator_options to allow users to control whether JSON paths following JSON operators in SQL statements should be obfuscated. By default, these paths are treated as literals and are obfuscated to ?.

For example, in the SQL statements

-- Extracts JSON object field with the given key
SELECT data::jsonb -> 'name'

The JSON path name following the JSON operator -> would normally be obfuscated to ?, resulting in:

SELECT data::jsonb -> ?

With the keep_json_path option enabled, users can skip this obfuscation, preserving the original JSON path name in the query.

Related change: DataDog/datadog-agent#29655

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Changelog entries must be created for modifications to shipped code
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.23%. Comparing base (c1e8530) to head (19544ae).

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
postgres	93.17% <ø> (+3.87%)	⬆️
presto	?
solr	?

Flags with carried forward coverage won't be shown. Click here to find out more.