Fix module name in error text at parse_xml filter

[matshch]

SUMMARY

Looks like error text in parse_xml filter was not changed after copy-pasting parse_cli filter. This pull request fixes module name in error text.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

parse_xml filter

ANSIBLE VERSION

ansible 2.6.2
  config file = None
  configured module search path = ['/home/al/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.5/dist-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609]

ADDITIONAL INFORMATION

While doing task with parse_xml filter, before:

fatal: [host.name]: FAILED! => {"msg": "unable to locate parse_cli template: /path/to/non/existing/template.yml"}

After:

fatal: [host.name]: FAILED! => {"msg": "unable to locate parse_xml template: /path/to/non/existing/template.yml"}

[ansibot]

cc @Qalthos @ganeshrn @gdpak @rcarrillocruz @trishnaguha
click here for bot help

[ganeshrn]

@matshch Needs updating unit tests

[matshch]

@ganeshrn looks like now tests passes

[Akasurde]

Closing and re-opening for CI trigger.

[ganeshrn]

@matshch Thank you!

[gundalow]

Hi,
I'm randomly selecting some PRs to see how it was for you, with the aim of making it easier for future contributors. As a new contributor I'm particularly interested as you don't have any prior knowledge of the Ansible process.

1. Generally speaking, how was the process for you?
2. Did it make sense what to do to progress the PR?
3. Did you read any of the developer (dev_guide) or contributor documentation?
4. What in the documentation was useful or confusing, missing or could be improved
5. Did you know you could run ansible-test locally?
6. What areas would you be interested in contributing to?

ansible/community#353