fix: remove unnecessary console logs and improve error handling in module services

Signed-off-by: Manuel Abascal <mjabascal10@gmail.com>

Author: mjabascal10

frontend/src/app/app-module/app-module-view/app-module-view.component.ts

@@ -92,7 +92,6 @@ export class AppModuleViewComponent implements OnInit, OnDestroy {
                   return res.body ? res.body.sort((a, b) => a > b ? 1 : -1) : [];
                 }),
                 catchError(error => {
-                    console.log(error);
                     this.utmToastService.showError('Failed to fetch categories',
                         'An error occurred while fetching module data.');
                     return of([]);
@@ -116,14 +115,12 @@ export class AppModuleViewComponent implements OnInit, OnDestroy {
   }
 
   filterByCategory($event: any) {
-    console.log('filter');
     this.req['moduleCategory.equals'] = $event;
     this.refreshModules();
 
   }
 
   onSearch($event: string) {
-    console.log('search');
     this.req.page = 0;
     this.req['prettyName.contains'] = $event;
     this.refreshModules();

frontend/src/app/app-module/services/module.service.ts

@@ -40,7 +40,6 @@ export class ModuleService {
     }),
     shareReplay(1),
     catchError(error => {
-      console.error(error);
       this.utmToastService.showError(
         'Failed to fetch servers',
         'An error occurred while fetching server list.'
@@ -84,7 +83,7 @@ export class ModuleService {
               m.prettyName = m.prettyName + ' GravityZone';
             }
           });
-          return response.body.filter(m => m.moduleName !== this.utmModulesEnum.AS_400);
+          return response.body;
         }),
       catchError(error => {
         console.error(error);