docs: complete the YARD tags on connection and run_command

[tas50]

Two documentation tag fixes found by auditing every method in lib/ against its real signature.

yard stats already reports 100.00% documented, but that number counts any docstring at all, so it does not catch a tag that is missing or a tag that names a class which does not exist. Auditing the parsed registry instead of the coverage percentage turns those up.

Transport::Docker#connection was missing @param block

The method is def connection(state, &block), but only state was documented, so the block did not appear in the generated signature. It is now documented as what it actually is: a proc forwarded to Connection.new, which yields the new connection to it. Worth stating explicitly that the connection is not closed when the block returns — Kitchen::Transport::Base::Connection#initialize only does yield self if block_given?.

CliHelper#run_command named a class that does not exist

The tag read @raise [Kitchen::ShellCommandFailed]. There is no such constant:

$ ruby -r kitchen -e 'Kitchen::ShellCommandFailed'
NameError: uninitialized constant Kitchen::ShellCommandFailed

The method raises a bare ShellCommandFailed, which resolves through the include ShellOut in CliHelper to Kitchen::ShellOut::ShellCommandFailed:

$ ruby -r kitchen/docker/helpers/cli_helper \
    -e 'puts Kitchen::Docker::Helpers::CliHelper.const_get(:ShellCommandFailed).name'
Kitchen::ShellOut::ShellCommandFailed

A type name that does not resolve renders as plain text rather than a link, so the tag pointed nowhere.

Verification

Auditing all 91 methods in the .yardopts scope (which includes --private --protected) for parameters absent from the @param tags:

before:  methods=91  missing_@param=1  missing_@return=0
after:   methods=91  missing_@param=0  missing_@return=0

yard emits no warnings before or after. lib/ was also swept for the other shapes of bad type name — Array[T] where YARD spells a list Array<T>, Hash[...] where it wants Hash{K => V}, and namespaced constants whose casing does not match the real class. Kitchen::ShellCommandFailed was the only hit; every other referenced constant resolves.

The doc and doc_coverage rake tasks already existed and still run clean.

$ bundle exec rake test
360 examples, 0 failures

$ cookstyle --chefstyle          # 9.0.0
44 files inspected, no offenses detected

Comments only — no behaviour change, and the test count is unchanged.

[RulerOf]

LGTM