feat: added optional opentelemetry tracer logging

[davearata-snorack]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [x] Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [x] Ensure the tests and linter pass
• [x] Code coverage does not decrease (if any source code was changed)
• [x] Appropriate docs were updated (if necessary)

Fixes #448 🦕

[google-cla[bot]]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[codecov[bot]]

Codecov Report

Merging #482 (a0b0fce) into master (70cd619) will increase coverage by 0.10%. The diff coverage is 95.23%.

@@            Coverage Diff             @@
##           master     #482      +/-   ##
==========================================
+ Coverage   93.56%   93.66%   +0.10%     
==========================================
  Files           4        4              
  Lines         497      537      +40     
  Branches       36       45       +9     
==========================================
+ Hits          465      503      +38     
- Misses         32       34       +2     

Impacted Files	Coverage Δ
src/index.ts	97.96% <95.23%> (-0.34%)	:arrow_down:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 70cd619...a0b0fce. Read the comment docs.

[google-cla[bot]]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[davearata-snorack]

@googlebot I signed it!

[0xSage]

@davearata-snorack can you edit your PR title per conventional commit semantics? The reason that's important is that this repo does auto release based on the types of changes committed for release.

[0xSage]

@davearata-snorack can you resolve conflicts in package.json? Drafting this PR in the meantime

[0xSage]

FYI, traceparent detection was implemented upstream in nodejs-logging here. Closing this PR as it's not needed for now - but feel free to reopen as the upstream impl was low level and we can always add additional otel support within this library.