fix(pg-instrumentation): capture query values when passed as second argument for prepared statements #3196
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
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: truewas enabled:Short description of the changes
args[1]) when the first argument is a query config object.db.postgresql.valuesis only recorded whenenhancedDatabaseReporting:true.$1,$2, etc.) remain indb.statement.