Logging consolidation - Remove window.console and console. calls

From the #9611 spike for #8527

⚠️ The DS part of the extension overrides window.console with their own messaging API, so make sure we don't impact them.

Check for console.log as well.

Direct uses of `console.`

DS - create an HTTP server to serve up React UI - Rewires console. calls to post messages to the web panel
- datascience-ui/react-common/postOffice.ts - console. calls overriden here
- webPanel.ts - console.log
- webPanelServer.ts- console.log
- datascience-ui/react-common/logger.ts - console.log
src/test/:
- exitCIAfterTestReporter.ts: for tests (CI/AzDO)
- utils/ts: for functional tests
- debuggerTest.ts: for debugger tests
- datascience/: DS tests
featureDeprecationManager.ts: notify deprecation (console.error) ➡️ can be moved to an output channel
socketServer.ts: error in socket server (console.error) ➡️ can be deleted
debugStreamProvider.ts: DA logging for third-party extension devs (console.error) ➡️ can be moved to a debug output channel
LocalDebugClient.ts: debugging error logging (console.error) ➡️ can be moved to a debug output channel
intellisenseDocument.ts: DS autocompletion (console.warn)
container.ts: for tests (console.warn) ➡️ use a logging function instead

Spoke to the DS team. We should not be replacing console.log inside DataScience-ui/react*

Data science portion of this will be cleaned up via #9832

Not making change to anything under debugAdapter. Since we are going to phase it out.

Anthony Kim (@anthonykim1)

took a look and these are the only places left with console.. Any of them worth keeping around or can I put in a PR to switch them all to trace?

These can all be switched to trace.