fix(logging): debug() should not use console.trace()

Problem:
The console.trace() docstring says:

    Prints to `stderr` the string 'Trace :', followed by the util.format
    formatted message and stack trace to the current position in the code.

But that is not useful/desirable for our codebase; we want
logger.debug() to write to the browser console (if available).

Solution:
Use console.debug() instead of console.trace().

Author: justinmk3

src/shared/logger/logger.ts

@@ -100,15 +100,15 @@ export class NullLogger implements Logger {
 }
 
 /**
- * Fallback to console.log() if getLogger() is requested before logging is fully initialized.
+ * Fallback used if {@link getLogger()} is requested before logging is fully initialized.
  */
 export class ConsoleLogger implements Logger {
     public setLogLevel(logLevel: LogLevel) {}
     public logLevelEnabled(logLevel: LogLevel): boolean {
         return false
     }
     public debug(message: string | Error, ...meta: any[]): number {
-        console.trace(message, ...meta)
+        console.debug(message, ...meta)
         return 0
     }
     public verbose(message: string | Error, ...meta: any[]): number {
@@ -123,6 +123,7 @@ export class ConsoleLogger implements Logger {
         console.warn(message, ...meta)
         return 0
     }
+    /** Note: In nodejs this prints to `stderr` (see {@link Console.error}). */
     public error(message: string | Error, ...meta: any[]): number {
         console.error(message, ...meta)
         return 0