Streaming support for Python

[GumpacG]

Adds streaming GraphBinary deserialization to the Python driver. Results are now deserialized directly from the HTTP response stream and pushed to the ResultSet individually, rather than buffering the entire response before processing.

Implements https://lists.apache.org/thread/qyxb845gy7fbhg87pmtcqs5zf0q33zm8

Changes:

• Added AiohttpSyncStream wrapper and get_stream() to transport, replacing read()
• Rewrote Connection._receive() to stream GB objects one-at-a-time via GraphBinaryReader.to_object()
• Updated ResultSet.one()/all() for individual item queue entries; added _EXHAUSTED sentinel to handle None as a valid Gremlin result
• Added content-type check before GB deserialization for non-GB error responses
• Removed dead code: buffered read(), data_received_aggregate, deserialize_message/read_payload, stream_chunk, max_content_length
• Removed GraphSON parameterized test fixtures
• Updated AbstractBaseTransport: read() → get_stream()
• 44 new unit tests covering streaming, bulking, error handling, content-type checks, and incremental delivery timing
• Updated CHANGELOG and upgrade docs
• Removed AbstractBaseTransport (gremlin_python.driver.transport)
• Removed AbstractBaseProtocol and GremlinServerHTTPProtocol (gremlin_python.driver.protocol)
• Removed protocol_factory parameter from Client, DriverRemoteConnection, and Connection
• Removed transport_factory parameter from Client, DriverRemoteConnection, and Connection
• GremlinServerError moved from gremlin_python.driver.protocol to gremlin_python.driver.connection
• Connection constructor signature changed — protocol and transport_factory positional args removed; serializer, auth, and interceptor options are now keyword arguments

Breaking changes:

• ResultSet iteration now yields individual items instead of lists. Code using results += result must change to
  results.append(result).
• read() replaced with get_stream()
• Connection constructor signature changed, protocol and transport_factory positional args removed; serializer, auth, and interceptor options are now keyword arguments
• Custom transport implementations are no longer supported — the driver uses AiohttpHTTPTransport directly

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.23%. Comparing base (cfd6889) to head (05cdc1d).
⚠️ Report is 1030 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3396      +/-   ##
============================================
- Coverage     77.87%   76.23%   -1.64%     
+ Complexity    13578    13318     -260     
============================================
  Files          1015     1011       -4     
  Lines         59308    59873     +565     
  Branches       6835     7011     +176     
============================================
- Hits          46184    45646     -538     
- Misses        10817    11541     +724     
- Partials       2307     2686     +379     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Cole-Greer]

Nit: I don't think it makes sense to compare to the Go driver here, technically go got HTTP streaming first in the TP4 betas, but these upgrade docs should focus on the perspective of TP3.8.x users upgrading to TP4. We will arguably want to rewrite all of these sections once all drivers are done, to either group all streaming updates together, or to better organize sections per-GLV.

For the purposes of this PR, I think we should just ensure we capture all the right information from that TP3 upgrade perspective, and then a larger restructuring can follow if/when it makes sense.