Extract console logging into Devlooped.Extensions.AI.Console (JSON only)

[Copilot]

Console logging was bundled in the core package, pulling Spectre.Console into all consumers. The change separates console concerns into a dedicated package while keeping tests in the main test project.

• New console package: Added Devlooped.Extensions.AI.Console project, moved JSON console logging extensions/options there, and removed Spectre.Console dependencies from the core library.
• Scope adjustment: Removed previously added YAML console rendering and its dependency to keep the package focused on JSON logging.
• Solution wiring: Updated solution and tests to reference the new console package (tests remain in the main test project).

Example:

builder
    .UseJsonConsoleLogging();

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Move console logging to separate package</issue_title>
<issue_description>Moving the JSON console logging to Devlooped.Extensions.AI.Console might make sense to reduce dependencies.

Perhaps we can also bring in the YAML logging we developed elsewhere too.

<agent_instructions>Create a separate packageable project with the console logging stuff, as well as the YAML rendering stuff. Tests (if any) should still live in the same project as today. </agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Move console logging to separate package #123

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[kzu]

@copilot remove the YAML aspect entirely

[Copilot]

@copilot remove the YAML aspect entirely

Removed the YAML console logging additions and their dependencies in ae3701f.