Update _BatchContext comment: clarify motivation is clean typing, not just circular import avoidance

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: Abel Milash

src/PowerPlatform/Dataverse/operations/batch.py

@@ -68,10 +68,11 @@ class _BatchContext(Protocol):
     """Structural interface required by batch operation namespaces.
 
     The operation namespaces (BatchRecordOperations, BatchTableOperations, etc.)
-    accept a ``_BatchContext`` rather than a concrete ``BatchRequest`` or
-    ``AsyncBatchRequest``, so that the same namespace classes can be reused by
-    both the sync and async batch implementations without importing either
-    concrete class — avoiding a circular dependency.
+    are pure (no I/O) and shared by both the sync and async batch implementations.
+    This Protocol allows them to type-annotate their ``batch`` parameter correctly
+    without importing either concrete class (``BatchRequest`` or
+    ``AsyncBatchRequest``), which would require ``# type: ignore`` or create a
+    circular import.
 
     Both :class:`~PowerPlatform.Dataverse.operations.batch.BatchRequest` and
     :class:`~PowerPlatform.Dataverse.aio.operations.async_batch.AsyncBatchRequest`