Improve messages when module/action loading fails after a redirect

[felixfontein]

SUMMARY

I've added a broken redirect community.docker.docker_container → community.dockerx.docker_container to investigate reports that the error messages are not helpful. The error message ansible produces is great. But ansible-doc and ansible-playbook are not helpful. This PR improves that a bit.

• ansible-doc now says

  [WARNING]: module docker_container was redirected to community.dockerx.docker_container, which was not found in XXX
  

  instead of

  [WARNING]: module docker_container not found in: XXX
  

• ansible-playbook now says

  ERROR! module/action 'docker_container' was redirected to 'community.dockerx.docker_container', which could not be loaded.
  

  instead of

  ERROR! couldn't resolve module/action 'docker_container'. This often indicates a misspelling, missing collection, or incorrect module path.
  

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

core

[felixfontein]

For lookups:

after:

fatal: [localhost]: FAILED! => {"msg": "lookup plugin 'community.docker.docker_container' was redirected to 'community.dockerx.docker_container', which could not be loaded"}

before:

fatal: [localhost]: FAILED! => {"msg": "lookup plugin (community.docker.docker_container) not found"}

[felixfontein]

I also tried to improve the messages for filter and test plugins, but the code there is somewhat strange - I have some doubts it will work for multi-stage redirects, and I was not able to change the error message in any way without removing the error and making debug output the untemplated expression...

I guess similar problems also happen for many other plugin types... Maybe a more unified mechanism for reporting such errors would be helpful :)

[ansibot]

The test ansible-test sanity --test pep8 [explain] failed with 1 error:

lib/ansible/parsing/mod_args.py:339:49: E121: continuation line under-indented for hanging indent

click here for bot help

[felixfontein]

/rebuild_failed