🧪 [testing improvement] Add error test for parse_command_arguments (v2)

This version includes proper formatting to satisfy the `black` linter, which caused a CI failure in the previous submission.

🎯 **What:** The testing gap addressed was the lack of validation for the JSON decoding error path.
📊 **Coverage:** The new tests cover:
- Passing `None` (returns empty dict)
- Passing valid JSON (returns parsed dict)
- Passing invalid JSON (raises `argparse.ArgumentTypeError`)
✨ **Result:** Improved reliability and code coverage for CLI argument parsing, now with lint-passing code.

Co-authored-by: rnovatorov <20299819+rnovatorov@users.noreply.github.com>

Author: google-labs-jules[bot]

tests/unit/test_cli/test_http/test_api/test_command_arguments.py

@@ -1,14 +1,22 @@
 import argparse
+
 import pytest
+
 from enapter.cli.http.api.command_arguments import parse_command_arguments
 
+
 def test_parse_command_arguments_none():
     assert parse_command_arguments(None) == {}
 
+
 def test_parse_command_arguments_valid_json():
-    assert parse_command_arguments('{"foo": "bar", "baz": 1}') == {"foo": "bar", "baz": 1}
+    assert parse_command_arguments('{"foo": "bar", "baz": 1}') == {
+        "foo": "bar",
+        "baz": 1,
+    }
+
 
 def test_parse_command_arguments_invalid_json():
     with pytest.raises(argparse.ArgumentTypeError) as excinfo:
-        parse_command_arguments('invalid json')
+        parse_command_arguments("invalid json")
     assert "Decode JSON:" in str(excinfo.value)