Add support for ansible-test sanity with docker

There have been several issues lately with using ansible-test sanity in the tox venv possibly related to a new github actions environment or a new version of ansible-test. The Galaxy team and Automation Hub use ansible-test sanity --docker. Let's use this for our tox CI.
The .github/workflows/tox.yml for each role will need to set

env:
  TOX_LSR: "git+https://github.com/linux-system-roles/[email protected]"
  LSR_ANSIBLE_TEST_DOCKER: "true"

to use docker in CI

Add support for ansible-test environment

Fix several issues with running ansible-test sanity from tox. You can now run tox -e collection,ansible-test to first build the collection then run ansible-test against it. ansible-test sanity is currently run with ansible 2.9 since that's what Automation Hub uses. See the README for more details.

lock down the version of ansible to ansible==2.10.* in tox-lsr, etc.

• additional fixes to run ansible-test in the collection test
• lock down the version of ansible to ansible==2.10.* in tox-lsr

improve collection testing, etc.

• runshellcheck.sh: Use find -exe
• runcollection.sh: Don't be so quiet
• lsr_ci_runtox: Don't exit too early
• improve collection testing
• update README with new *_CONFIG_FILE env. vars

add six to deps for collection

add six to deps for collection

minor docs fix

minor docs fix

support for ansible-doc, ansible-test in collections testing

the tox -e collection testenv is now able to run ansible-doc and ansible-test. You can enable this by setting the environment variable LSR_ROLE2COLL_RUN_ANSIBLE_TESTS=true - see the docs for more details

support for molecule v3

support for molecule v3

lock role2collection version

lock the lsr_role2collection script to a specific version. This
will allow us to change the script without immediately breaking
CI. Introduce env. vars. for the script version, namespace, and
collection name.

molecule: remove ansible-lint, add jmespath

molecule: remove ansible-lint, add jmespath