fix(puppetdb): handle undefined latest_report_status in transformer

Fixes #25224

The defaultResourceTransformer crashes when latest_report_status is undefined
because it's not present in /factsets endpoint response (only in /nodes).

This adds optional chaining (?.) to safely handle undefined values.

Signed-off-by: Jamal Sebbari <jsebbari@splio.com>

plugins/catalog-backend-module-puppetdb/src/puppet/transformers.ts

@@ -51,12 +51,10 @@ export const defaultResourceTransformer: ResourceTransformer = async (
       description: node.facts?.data
         ?.find(e => e.name === 'ipaddress')
         ?.value?.toString(),
-      tags: kernel
-        ? [
-            kernel.toString().toLocaleLowerCase('en-US'),
-            latest_report_status.toString().toLocaleLowerCase('en-US'),
-          ]
-        : [],
+      tags: [
+        kernel?.toString().toLocaleLowerCase('en-US'),
+        latest_report_status?.toString().toLocaleLowerCase('en-US'),
+      ].filter((tag): tag is string => Boolean(tag)),
     },
     spec: {
       type: type,