fix: streamline loading state management in playbook service and clean up filter parameters in playbooks component

Signed-off-by: Manuel Abascal <[email protected]>

Author: mjabascal10

frontend/src/app/incident-response/playbooks/playbooks.component.ts

@@ -32,8 +32,7 @@ export class PlaybooksComponent implements OnInit, AfterViewInit, OnDestroy {
     sort: '',
     'active.equals': null,
     'agentPlatform.equals': null,
-    'createdBy.equals': null,
-    'systemOwner.equals': false
+    'createdBy.equals': null
   };
   platforms: string[];
   users: string[];

frontend/src/app/incident-response/shared/services/playbook.service.ts

@@ -20,7 +20,7 @@ export class PlaybookService {
   playbooks$ = this.request$.pipe(
     filter(request =>  !!request),
     switchMap(request => {
-      setTimeout(() => this.loading.next(true), 300);
+      this.loading.next(true);
       return this.incidentResponseRuleService.query(request).pipe(
         map(response => {
           this.totalItems.next(Number(response.headers.get('X-Total-Count')));
@@ -30,7 +30,7 @@ export class PlaybookService {
           this.utmToastService.showError('Error', 'An error occurred while fetching playbooks.');
           return of([]);
         }),
-        finalize(() =>  setTimeout(() => this.loading.next(false), 200))
+        finalize(() =>  this.loading.next(false))
       );
     })
   );