fix(otlp-transformer): add check for possible unsafe json parse

[maryliag]

JSON.parse() on server responses without try/catch will throw on malformed data, potentially crashing the process

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.76%. Comparing base (36ce569) to head (77505f6).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6588   +/-   ##
=======================================
  Coverage   95.75%   95.76%           
=======================================
  Files         375      375           
  Lines       12725    12737   +12     
  Branches     3013     3013           
=======================================
+ Hits        12185    12197   +12     
  Misses        540      540           

Files with missing lines	Coverage Δ
...al/packages/otlp-transformer/src/logs/json/logs.ts	100.00% <100.00%> (ø)
...kages/otlp-transformer/src/metrics/json/metrics.ts	100.00% <100.00%> (ø)
.../packages/otlp-transformer/src/trace/json/trace.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trentm]

potentially crashing the process

It looks to me like the only caller of this is wrapping in a try/catch already.

opentelemetry-js/experimental/packages/otlp-exporter-base/src/otlp-export-delegate.ts

Line 90 in 8ee2a8b

this._serializer.deserializeResponse(response.data)

Perhaps it is more appropriate for an exception to be caught in the caller? I haven't looked closely.