feat: add error level mapping support for upstream sync

- Add level parameter to error messages (defaults to 'error')
- Add _get_level() helper function
- Freightcom API v2 does not provide level field, so defaults to 'error'
- Required for upstream sync with karrio-community (commit 1a1b158)

Author: jacobshilitz

plugins/freightcom_rest/karrio/providers/freightcom_rest/error.py

@@ -26,10 +26,20 @@ def parse_error_response(
                 if (error.get("details", {}) or error.get("data", {}))
                 else error.get("message")
             ),
+            level=_get_level(error),
             details={
                 **kwargs,
                 **(error.get('data', {}))
             },
         )
         for error in errors
     ]
+
+
+def _get_level(error: dict, default_level: str = "error") -> str:
+    """Map Freightcom error response to standardized level.
+    
+    Freightcom API v2 does not provide a level field in error responses.
+    All error responses default to "error" level.
+    """
+    return default_level

plugins/freightcom_rest/tests/freightcom_rest/test_rate.py

@@ -449,7 +449,8 @@ def test_parse_error_response(self):
         {
             "carrier_id": "freightcom_rest",
             "carrier_name": "freightcom_rest",
-            "message": "Unable to get rates",
+            "message": "Unable to get rates: services: invalid-syntax",
+            "level": "error",
             "details": {
                 "services": "invalid-syntax"
             }