fix: Fix an issue where logging configuration could over-match for log records without a message or severity.

[kinyoklion]

Summary

The CustomSampler errantly checked if message and severity were of the correct type before attempting to match them. If they were not, then they matched. The simplest solutions is to not do the check. Alternatively it could do the check, and when the type is not string they do not match.

How did you test this change?

Unit tests.

Other

After this PR is non-js SDKs should have their JSON files updated. I did not update in this PR because I didn't want to trigger a release of those SDKs.

---

Note

Ensure log rules requiring message/severity only match when the record has a string message/severity; add scenarios and test helpers across SDKs.

• Sampling logic:
  • Go (go/internal/otel/custom_sampler.go): In matchesLogConfig, require record.Body() to be KindString for message matching; return false otherwise.
  • JS/TS (Node, Shared, Highlight Run): Simplify matchesLogConfig by removing permissive typeof gates; Shared explicitly rejects non-string record.body for message matching.
• Tests:
  • Add log scenarios that verify configs with both message and severityText do not match when logs are empty, only have message, or only have severity (in Go/Node/Shared/Highlight Run JSONs).
  • Introduce helper to construct ReadableLogRecord from scenario input in Node/Shared tests and update usages.

^{Written by Cursor Bugbot for commit 67c9367. This will update automatically on new commits. Configure here.}

[kinyoklion]

bugbot review