feat(opentelemetry-plugin-pg): omit pg.values by default

[sergioregueira]

Which problem is this PR solving?

This PR solves issue #11, that reports the PostgreSQL plugin must not log pg.values by default because they may contain sensitive data such as user credentials.

Short description of the changes

1. I fixed eslint warnings found in master.
2. I refactored the PgClientExtended type to inherit directly from pgTypes.Client instead of intersect them all the time.
3. I documented arguments of several methods of utils.ts to avoid generic types (...args: unknown[])
4. I renamed PgPluginQueryConfig interface to NormalizedQueryConfig (based on the plugin) to avoid confusion.
5. I changed implementation to log pg.values only when enhancedDatabaseReporting (standard property) flag is se to true.
6. I implemented several unit tests that validate the behavior of that flag creating a new specific test files for utils.ts instead of duplicating the assertions for each valid call.

[codecov]

Codecov Report

Merging #174 into master will increase coverage by 0.07%.
The diff coverage is 98.85%.

@@            Coverage Diff             @@
##           master     #174      +/-   ##
==========================================
+ Coverage   94.23%   94.30%   +0.07%     
==========================================
  Files          76       77       +1     
  Lines        3766     3830      +64     
  Branches      406      413       +7     
==========================================
+ Hits         3549     3612      +63     
- Misses        217      218       +1     

Impacted Files	Coverage Δ
...ugins/node/opentelemetry-plugin-pg/test/pg.test.ts	94.37% <ø> (ø)
...ns/node/opentelemetry-plugin-pg/test/utils.test.ts	98.36% <98.36%> (ø)
plugins/node/opentelemetry-plugin-pg/src/pg.ts	91.66% <100.00%> (+0.28%)	⬆️
plugins/node/opentelemetry-plugin-pg/src/utils.ts	97.01% <100.00%> (+0.04%)	⬆️

[vmarchaud]

lgtm

[dyladan]

This looks like great work thanks!

[obecny]

lgtm