Improve error output when calls to ansible-doc or ansible --version fail

[felixfontein]

Before:

subprocess.CalledProcessError: Command '['ansible-doc', '-vvv', '--metadata-dump', '--no-fail-on-errors', 'ansible.builtin', 'community.sops', 'foo.bar']' returned non-zero exit status 1.

After:

RuntimeError: The command
| ansible-doc -vvv --metadata-dump --no-fail-on-errors ansible.builtin community.sops foo.bar
returned exit status 1 with error output:
| [WARNING]: You are running the development version of Ansible. You should only
| run Ansible from "devel" if you are modifying the Ansible engine, or trying out
| features under development. This is a rapidly changing source of code and can
| become unstable at any point.
| ERROR! Cannot use supplied collection foo.bar: unable to locate collection foo.bar. unable to locate collection foo.bar

This would have helped me to quickly identify two nightly CI failures indirectly caused by ansible-core 2.16.0 having been released. (The lint-collection-docs subcommand was used when the collection's dependencies haven't been installed, and antsibull-docs was trying to find the docs for the dependencies as well. After figuring out that this caused the ansible-doc call to suddenly fail, it was easy to fix it by making sure that all dependent collections are installed.)

[felixfontein]

(One of the nightly CI failures: https://github.com/ansible-collections/community.routeros/actions/runs/6780358129/job/18459784750)

[samccann]

Can't comment on the code but the word-parts LGTM :-)

[felixfontein]

@samccann thanks for reviewing the messages :)