fix(instrumentation-pg): normalize leading/trailing spaces in database operation name

[ecarrizo2]

Which problem is this PR solving?

This PR intends to solves bug #3265.
Removing leading and trailing whitespaces when parsing and extracting the command from query text.

Actual Behavior:
When calling get query span name with leading spaces in the query text, the spaces are translated into the Span
e.g utils.getQuerySpanName('dbName', { text: ' SELECT $1' }) results in pg.query: SELECT dbName

Intended Behavior
Leading spaces are removed utils.getQuerySpanName('dbName', { text: ' SELECT $1' }) results in pg.query: SELECT dbName

Short description of the changes

• Add a new command to trim the queryText to remove leading/trailing whitespaces before extracting the SQLCommand out of it
• Added new tests to cover the problematic scenarios provided in the issue instrumentation-pg: operation name should be trimmed #3265

Offtopic and other notes

While reviewing other modules also found that packages/instrumentation-mysql/src/utils.ts and packages/instrumentation-mysql2/src/utils.ts use similar methods that may need revision.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pichlermarc / name: Marc Pichler (ab347fa)

[otelbot]

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