fix(pg-instrumentation): capture query values when passed as second argument for prepared statements

[aryamohanan]

Which problem is this PR solving?

Fixes #3193

When using prepared statements with the following syntax, query parameter values were not captured even when enhancedDatabaseReporting: true was enabled:

client.query(
  { name: 'statement_name', text: 'SELECT * FROM pg_tables WHERE schemaname = $1' },
  ['public']
);

Short description of the changes

• Fixed missing parameter values when executing prepared statements.
• Updated instrumentation to correctly read values from the second argument (args[1]) when the first argument is a query config object.
• Ensured that db.postgresql.values is only recorded when enhancedDatabaseReporting:true.
• Maintained query text sanitization, placeholders ($1, $2, etc.) remain in db.statement.

[aryamohanan]

@maryliag Could you please take a look at this PR? TIA

[maryliag]

I like the suggestion on the issue itself, of just updating the line 342 to
values: (arg0 as any).values ?? (Array.isArray(args[1]) ? args[1] : undefined),, this way it avoids doing some repetition on checks, which is what you're doing here.

Would you mind making that solutions instead and checking if the tests will work as expected?

[maryliag]

Awesome! Thank you!

[otelbot]

Thank you for your contribution @aryamohanan! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.