feat(@angular-devkit/core): jobs should re-log instead of forwarding

Current behaviour is to have logs forwarded, but this is flawed because on the
job side the logger is actually re-created. This allows logs to be actually part
of the caller side logging infrastructure.

Author: hansl

packages/angular_devkit/core/src/experimental/jobs/create-job-handler.ts

@@ -101,7 +101,7 @@ export function createJobHandler<A extends JsonValue, I extends JsonValue, O ext
       });
 
       // Configure a logger to pass in as additional context.
-      const logger = new Logger('job');
+      const logger = new Logger('-internal-job-logger-');
       const logSub = logger.subscribe(entry => {
         subject.next({
           kind: JobOutboundMessageKind.Log,

packages/angular_devkit/core/src/experimental/jobs/simple-scheduler.ts

@@ -305,7 +305,7 @@ export class SimpleScheduler<
     let state = JobState.Queued;
     let pingId = 0;
 
-    const logger = options.logger ? options.logger.createChild('job') : new NullLogger();
+    const logger = options.logger ? options.logger : new NullLogger();
 
     // Create the input channel by having a filter.
     const input = new Subject<JsonValue>();
@@ -349,7 +349,8 @@ export class SimpleScheduler<
 
         switch (message.kind) {
           case JobOutboundMessageKind.Log:
-            logger.next(message.entry);
+            const entry = message.entry;
+            logger.log(entry.level, entry.message, entry);
             break;
 
           case JobOutboundMessageKind.ChannelCreate: {