feat: Log resource when exception occurs to aid debugging (#172)

This change will allow plugin authors to see the resource that caused the exception, helping them find the underlying cause. To get this level of information, `--log-level debug` needs to be passed to the plugin server (or the CLI, depending on whether or not the plugin is run using the grpc registry)

Closes cloudquery/cloudquery#18002

cloudquery/sdk/scheduler/scheduler.py

@@ -116,6 +116,12 @@ def resolve_table(
                         depth=depth,
                         exc_info=e,
                     )
+                    self._logger.debug(
+                        "details about resource that failed to resolve",
+                        client_id=client.id(),
+                        table=resolver.table.name,
+                        resource=item,
+                    )
                     continue
                 res.put(SyncInsertMessage(resource.to_arrow_record()))
                 for child_resolvers in resolver.child_resolvers: