Replace console spying in tests with in-memory exporters

[sjvans]

Tests should read telemetry from in-memory exporters (like MyInMemorySpanExporter, introduced in #465) rather than spying on console.dir / cds.test.log() and parsing formatted output. Console spying is brittle (couples tests to exporter formatting), order-sensitive, and — as the jest→vitest migration (#474) showed — sensitive to log-timing windows.

The console-based tests fall into three groups; handle each accordingly.

1. Trace-span tests still spying on console.dir → use MyInMemorySpanExporter

These use the sdk-trace-node console exporter (tracing-console / formerly tracing-attributes profile) and read spans out of the console.dir spy. They should switch to the tracing-in-memory profile and read captured from MyInMemorySpanExporter (as tracing.test.js, tracing-mt.test.js, tracing-scheduled.test.js etc. already do post-#465):

• test/tracing-remote-cloudsdk.test.js (getSpans/getCapSpans off console.dir → captured)
• test/tracing-remote-native.test.js (same)
• test/tracing-span-names.test.js (same)

Once these move off it, the tracing-console profile (@opentelemetry/sdk-trace-node console exporter) in test/bookshop/.cdsrc.json may become unused — remove it if so. (Note: there's a separate deferred task to rename that profile; this supersedes it — it just goes away.)

2. Metric tests spying on console.dir → need an in-memory metric reader

#465 only added an in-memory span exporter; there is no metric equivalent yet. These read metric datapoints (descriptor.name, dataPoints) out of the ConsoleMetricExporter console.dir output:

• test/metrics-outbox.test.js
• test/metrics-outbox-multitenant.test.js
• test/metrics-outbox-disabled.test.js

Add a MyInMemoryMetricReader (companion to MyInMemorySpanExporter, wired via a .cdsrc.json profile) that captures the exported ResourceMetrics in a module-level array, and convert these three tests to assert against it. forceFlush() on the reader replaces the current sleep+scrape pattern.

3. Genuine console-output tests → LEAVE AS-IS

These legitimately assert on what is printed to the console, which is the behavior under test — not a backdoor to spans/metrics. Do NOT convert:

• test/metrics.test.js — asserts the ConsoleMetricExporter's host-metrics text output (process/network/nodejs.eventloop.* lines). This is testing the console formatter itself.
• test/logging.test.js — asserts the LogRecord objects the logging path emits (body, exception.* attributes). (If a MyInMemoryLogRecordExporter is ever added, revisit; not required here.)

Definition of done

• No jest.spyOn(console, ...) / console.dir = … / cds.test.log() span-scraping in the tracing tests (group 1).
• Metric-outbox tests (group 2) assert via an in-memory metric reader, no consoleDirLogs.
• Groups 3 remain, with a one-line comment noting they intentionally test console output.
• Related: builds on feat: trace queue worker transactions + structured span test infrastructure #465 (span exporter); coordinate with chore: migrate test runner from jest to vitest #474 (vitest) which already touched several of these files.

[sjvans]

Folding in PR #445. #445 ('more stable outbox metrics tests') targets the same 3 metrics-outbox files (group 2 here) with a state-based expectEventually() + forceFlush() polling helper that replaces the wait(150)/wait(600) sleeps. That's the right idea for killing the timing flakiness, but only half of this issue — it keeps the console.dir spy. The group-2 work here should combine both: introduce MyInMemoryMetricReader (kill the console spy) and carry over #445's expectEventually/forceFlush polling (kill the sleeps). #445 is behind develop and its metrics tests were since rewritten by #465, so rather than rebase it standalone, its approach is absorbed here.

[sjvans]

Group 2 done via #479 (merged): added MyInMemoryMetricReader (DELTA-temporality, companion to MyInMemorySpanExporter) and converted metrics-outbox.test.js, metrics-outbox-multitenant.test.js, metrics-outbox-disabled.test.js off the console.dir spy onto it + expectEventually polling.

Note on group 3: #479 also converted metrics.test.js — but split it rather than leaving it, which preserves the intent. The ConsoleMetricExporter formatting is now unit-tested directly in the new test/console-metric-exporter.test.js, while metrics.test.js became a collection integration test on the reader. No console-formatter coverage lost.

Still open — group 1: tracing-remote-cloudsdk.test.js, tracing-remote-native.test.js, tracing-span-names.test.js still spy on console.dir and need to move to the tracing-in-memory profile / MyInMemorySpanExporter. Leaving this issue open for that.