Fix CleanLogMessage

[yashnevatia]

Agent:

The intent is fine; the implementation was sloppy — no word boundary, so ts= matched inside lamports=, assets=, events=, metrics=, anywhere …ts= shows up as a substring. Same risk exists for level= (anything ending in level=, e.g. loglevel=), but ts= is the worst offender because it's only 3 characters and -rts$ / -ets$ / -its$ word endings are common.

The \b fix anchors each pattern to start at a word boundary — so only standalone ts=... fields get stripped, not substrings buried inside user content.

echo "lamports=5000000000" | grep -oE 'ts=\S+'
# prints: ts=5000000000   ← yep, that's what was getting stripped

[github-actions]

👋 yashnevatia, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!