TASK: Show rendering error details in render_orchestrator output

This stops having to go through all individual worker outputs

Author: Sebobo

Classes/NodeRendering/NodeRenderOrchestrator.php

@@ -223,10 +223,11 @@ public function renderContentRelease(ContentReleaseIdentifier $contentReleaseIde
             // This is to gain better visibility into all errors currently happening; and thus maybe being able to see
             // patterns among the errors.
             // We also do NOT start a new incremental release, as this would lead very likely to the same errors.
-            $amountOfRenderingErrors = count($this->redisRenderingErrorManager->getRenderingErrors($contentReleaseIdentifier));
+            $renderingErrors = $this->redisRenderingErrorManager->getRenderingErrors($contentReleaseIdentifier);
+            $amountOfRenderingErrors = count($renderingErrors);
             if ($amountOfRenderingErrors > 0) {
                 $this->redisContentReleaseService->setContentReleaseMetadata($contentReleaseIdentifier, $releaseMetadata->withStatus(NodeRenderingCompletionStatus::failed()), RedisInstanceIdentifier::primary());
-                $contentReleaseLogger->error('In this iteration, there happened ' . $amountOfRenderingErrors . ' rendering errors. EXITING now, as there is no chance of completing the content release successfully.');
+                $contentReleaseLogger->error('In this iteration, there happened ' . $amountOfRenderingErrors . ' rendering errors. EXITING now, as there is no chance of completing the content release successfully.', [$renderingErrors]);
                 yield ExitEvent::createWithStatusCode(self::EXIT_ERRORSTATUSCODE_RENDERING_ERRORS);
                 return;
             }