Fixes #766.

Custom formatter output is inlined into the first format argument, then interpreted again by Node's util.formatWithOptions or the browser console. Percent sequences inside inspected objects were therefore treated as new format specifiers and consumed trailing arguments.

This stringifies formatter results and escapes their percent signs before inlining them. The downstream formatting pass converts %% back to literal %, preserving the formatter output and leaving subsequent arguments untouched. Explicit %% sequences in the user's original format string still follow the existing path unchanged.

Validation:

• npm run test:node -- --reporter dot — 18 passing
• XO on the changed files under Node 20 — no errors (existing warnings only)
• regression coverage for both the Node %o formatter and the shared custom formatter path

The repository's pinned XO stack does not run on Node 24 because a transitive dependency calls the removed util.isDate; lint was therefore run with Node 20.