fix: run every docker command through sudo when use_sudo is set

[tas50]

Reported behaviour: use_sudo: true does not help on a host where the Docker daemon socket needs root -- the very case the README points at it for.

The bug

use_sudo reached exactly one command: the bare docker probe in verify_dependencies.

Kitchen's ShellOut#run_command treats sudo as a per-call option -- it reads :use_sudo out of the options hash it is handed and knows nothing about config. docker_command builds its own command line and never passed it along, so every build, run, port, inspect, exec, cp, and rm still ran as the invoking user.

The result is the worst shape of failure: the probe succeeds under sudo, so the driver reports Docker is usable, and kitchen create then dies on the first command that actually touches the daemon.

The transport is affected the same way and separately: it is its own plugin with its own config, and it runs docker exec and docker cp. Fixing only the driver would have moved the failure from create to converge.

The fix

• docker_command adds the sudo options when use_sudo is set.
• sudo_command is honoured, for hosts that use something other than sudo -E (doas, a wrapper script).
• The transport gains both options, and the README says to set them in both places.

Confirmation

Reproduced against Docker 29.7.2 (Docker Desktop 4.87.0, macOS/arm64) with Test Kitchen 4.1.1, using a docker wrapper on PATH that refuses unless it was launched through sudo -- so a run can only succeed if every command went through it:

driver:
  name: docker
  binary: dockerwrap
  use_sudo: true
transport:
  name: docker
  binary: dockerwrap
  use_sudo: true

Before:

       permission denied while trying to connect to the Docker daemon socket
>>>>>> Message: 1 actions failed.

After -- full kitchen converge against a real ubuntu-24.04 container:

       HELLO FROM PROVISIONER
       Finished converging <default-ubuntu-2404> (0m0.63s).

with 14 recorded sudo invocations (the probe plus 13 real docker commands) where there had been 1.

rake style clean; rspec 313 examples, 0 failures (6 new).