DEVPROD-18354: Fix log ingestion memory bug

[sophstad]

DEVPROD-18354

Description

Improve duplicated log data by using a callback from the stream instead of an extra state.

Also update resmoke processing to create new strings with no references to what was ingested, allowing for proper garbage collection.

Note that this fix is not exactly viable in Firefox: Firefox's TextDecoder.decode() parses into UTF-16 which uses 2x the storage 😩

Testing

Validated via memory heap snapshot

Original:

Fix:

[sentry]

Bug: Moving the stateful AnsiUp instance to a module-level singleton will cause color state to leak between log rows, resulting in incorrect rendering.
_{Severity: MEDIUM}

Suggested Fix

Revert to creating a new AnsiUp instance for each row. To optimize performance, create a per-component instance using useMemo(() => new AnsiUp(), []). This isolates the state to each row while avoiding re-creation on every render.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: apps/parsley/src/components/LogRow/AnsiRow/index.tsx#L13-L14

Potential issue: The `AnsiUp` library is stateful, meaning color settings persist across
calls. By changing its instantiation from per-component to a single module-level
instance, the component now shares state across all log rows. If a log line sets a color
without resetting it at the line's end, a common case in CI logs, that color will
"bleed" into subsequent, unrelated log lines. This will cause visual corruption and
misrepresentation of log data, which is a core function of the application.

_{Did we get this right? 👍 / 👎 to inform future reviews.}