Fix: ConsoleLogger.warn/error swallow their second argument

[pjrobertson]

The Logger interface declares warn(message, more?), and ~10 call sites pass a caught error as that second arg (e.g. logger.warn(\Plugin ${plugin.name} extractContextFromExpression
failed:, err)inkey-finder.ts). But ConsoleLogger.warnonly forwarded the message toconsole.warn, so plugin-hook errors printed as a bare ... failed:with no detail (see screenshot). This forwards the optional second arg on bothwarnanderror, leaving single-arg output unchanged.

Adds test/console-logger.test.ts. Note: 2 pre-existing failures in test/status.test.ts are unrelated (fail on main too).

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

• motivation/reason is provided
• commit message and code follows the Developer's Certification of Origin

[adrai]

thx, included in v1.66.1