Refactor error_response function for improved argument handling

- Enhanced the `error_response` function to support backward compatibility by normalizing arguments when positional arguments are misused.
- Updated various views to pass `None` for the `errors` parameter in `error_response` calls, ensuring consistent response formatting.
- Adjusted logging in `ContentSyncService` and `WordPressClient` to use debug level for expected 401 errors, improving log clarity.
- Removed deprecated fields from serializers and views, streamlining content management processes.

backend/igny8_core/utils/wordpress.py

@@ -457,7 +457,11 @@ class WordPressClient:
                     }
                     for prod in products
                 ]
-            logger.warning(f"Failed to fetch products: HTTP {response.status_code}")
+            # Log as debug if 401 (expected if WooCommerce not configured)
+            if response.status_code == 401:
+                logger.debug(f"WooCommerce products require authentication: HTTP {response.status_code}")
+            else:
+                logger.warning(f"Failed to fetch products: HTTP {response.status_code}")
             return []
         except Exception as e:
             logger.error(f"Error fetching WooCommerce products: {e}")
@@ -533,7 +537,11 @@ class WordPressClient:
                     }
                     for cat in categories
                 ]
-            logger.warning(f"Failed to fetch product categories: HTTP {response.status_code}")
+            # Log as debug if 401 (expected if WooCommerce not configured)
+            if response.status_code == 401:
+                logger.debug(f"WooCommerce product categories require authentication: HTTP {response.status_code}")
+            else:
+                logger.warning(f"Failed to fetch product categories: HTTP {response.status_code}")
             return []
         except Exception as e:
             logger.error(f"Error fetching WooCommerce product categories: {e}")