What do these changes do?

As a follow-up to #983, this PR makes timeout handling consistent across all long-running Docker API operations by adding an explicit timeout parameter to methods that previously lacked one and fixing the timeout implementation to properly handle both total and socket_read timeouts.

The following operations now accept a timeout parameter with infinite timeout defaults:

• DockerContainer.log() - for streaming container logs
• DockerContainer.attach() - for attaching to container streams
• DockerContainer.stats() - for streaming container statistics
• DockerImages.build() - for building images (Add timeout support with improved documentation #983)
• DockerImages.export_image() - for exporting images as tarballs
• DockerImages.import_image() - for importing image tarballs
• DockerImages.push() - for pushing image to registry (Add timeout support with improved documentation #983)
• DockerImages.pull() - for pull image from registry (Add timeout support with improved documentation #983)
• DockerLogs.run() - for log streaming (Add timeout support with improved documentation #983)
• DockerContainer.commit() (Add missing consistent client timeout in DockerContainer.commit() #992)

Additionally, the timeout handling in Docker._query() has been fixed to set both total and sock_read consistently when a float timeout is provided, preventing timeout inconsistencies that could cause operations to fail prematurely.

Now all above methods consistently use the new base method _resolve_long_running_timeout() which selectively overrides total and sock_read timeout values while preserving other timeouts such as connection establishment from self.docker._timeout.

Are there changes in behavior for the user?

New functionality:

• Users can now explicitly control timeouts for long-running operations like build, import, export, logs, attach, and stats.
• These operations default to infinite timeout (both total=None and sock_read=None), which matches the expected behavior for potentially long-running Docker operations.

Behavior change:

• When passing a float timeout value to any Docker API method, both the total timeout AND socket read timeout are now set to that value (previously only total was set). This ensures more consistent timeout behavior but may cause some operations to timeout differently than before.

Deprecation notice:

• The deprecation warning message for float timeouts has been updated to encourage using asyncio.timeout() block or passing aiohttp.ClientTimeout objects instead of float values.

Related issue number

N/A

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• Add a new news fragment into the changes folder