fix(api): Update DiagLogger to use original console methods

[martinkuba]

Which problem is this PR solving?

In the browser repo, we are introducing an instrumentation for capturing console logs. There is an issue with the diagnostics logger - capturing console logs triggers work by the SDK, which may generate console logs using the diagnostics logger, which creates more work by the SDK ... infinite loop.

The issue has been discussed here.

This is an alternative fix to #6355

Short description of the changes

The original console methods are saved at module load time in DiagConsoleLogger. This prevents diagnostic log calls
from being re-captured as telemetry.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.50%. Comparing base (fcafab5) to head (cc36318).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6395   +/-   ##
=======================================
  Coverage   95.50%   95.50%           
=======================================
  Files         365      365           
  Lines       11609    11618    +9     
  Branches     2677     2680    +3     
=======================================
+ Hits        11087    11096    +9     
  Misses        522      522           

Files with missing lines	Coverage Δ
api/src/diag/consoleLogger.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[martinkuba]

@pichlermarc This is related to the comment above about console available only when developer console is open. I think this would happen only in some very old browsers like IE. We only support modern browsers, so this is purely defensive. But the logic was already there before this change (comment on line 65).