##### SUMMARY
in the module documentation we have the return value set to `before` and `after` and `commands` for all resource modules.  At some point this changed for only junos resource modules, and only for the parameter `commands`.  It has been changed to `xml`.  I think this *should* be *commands* and just return the xml payload under the variable named *commands*

this file can be found here: https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py#L80

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME
junos_l3_interfaces
junos_l2_interfaces
probably all junos resource modules

##### ANSIBLE VERSION
```paste below
latest dev
```

##### CONFIGURATION
```paste below
DEFAULT_HOST_LIST(/home/student1/.ansible.cfg) = [u'/home/student1/networking-workshop/lab_inventory/hosts']
DEFAULT_STDOUT_CALLBACK(/home/student1/.ansible.cfg) = yaml
DEFAULT_TIMEOUT(/home/student1/.ansible.cfg) = 60
DEPRECATION_WARNINGS(/home/student1/.ansible.cfg) = False
HOST_KEY_CHECKING(/home/student1/.ansible.cfg) = False
PERSISTENT_COMMAND_TIMEOUT(/home/student1/.ansible.cfg) = 60
PERSISTENT_CONNECT_TIMEOUT(/home/student1/.ansible.cfg) = 60
RETRY_FILES_ENABLED(/home/student1/.ansible.cfg) = False
```

##### OS / ENVIRONMENT
RHEL 7.6

##### STEPS TO REPRODUCE
```yaml
[student1@ansible ~]$ cat junos.yml
---
- hosts: rtr3
  gather_facts: false
  tasks:
    - name: grab info
      junos_facts:
        gather_subset: min
        gather_network_resources: l3_interfaces

    - debug:
        var: ansible_network_resources
```

<!--- HINT: You can paste gist.github.com links for larger files -->

##### EXPECTED RESULTS
the variable `commands` would return the payload versus the variable named `xml` that is not documented

like this
```
TASK [ensure that the IP address information is accurate] ***********************************************************************
 [WARNING]: Platform linux on host rtr3 is using the discovered Python interpreter at /usr/bin/python, but future installation
of another Python interpreter could change this. See
https://docs.ansible.com/ansible/devel/reference_appendices/interpreter_discovery.html for more information.

changed: [rtr3] => changed=true
  after:
  - name: lo0
    unit: '0'
  ansible_facts:
    discovered_interpreter_python: /usr/bin/python
  before:
  - ipv4:
    - address: 10.10.10.1/24
    ipv6:
    - address: fc00::100/64
    - address: fc00::101/64
    name: lo0
    unit: '0'
  commands:
  - <nc:interfaces xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:interface><nc:name>lo0</nc:name><nc:unit><nc:name>0</nc:name><nc:family><nc:inet><nc:address delete="delete"/></nc:inet><nc:inet6><nc:address delete="delete"/></nc:inet6></nc:family></nc:unit></nc:interface></nc:interfaces>
```

##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->

<!--- Paste verbatim command output between quotes -->
```paste below
TASK [ensure that the IP address information is accurate] ***********************************************************************
 [WARNING]: Platform linux on host rtr3 is using the discovered Python interpreter at /usr/bin/python, but future installation
of another Python interpreter could change this. See
https://docs.ansible.com/ansible/devel/reference_appendices/interpreter_discovery.html for more information.

changed: [rtr3] => changed=true
  after:
  - name: lo0
    unit: '0'
  ansible_facts:
    discovered_interpreter_python: /usr/bin/python
  before:
  - ipv4:
    - address: 10.10.10.1/24
    ipv6:
    - address: fc00::100/64
    - address: fc00::101/64
    name: lo0
    unit: '0'
  xml:
  - <nc:interfaces xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:interface><nc:name>lo0</nc:name><nc:unit><nc:name>0</nc:name><nc:family><nc:inet><nc:address delete="delete"/></nc:inet><nc:inet6><nc:address delete="delete"/></nc:inet6></nc:family></nc:unit></nc:interface></nc:interfaces>
```

#
"""
The junos_lldp_interfaces class
It is in this file where the current configuration (as dict)
is compared to the provided configuration (as dict) and the command set
necessary to bring the current configuration to it's desired end-state is
created
"""
from __future__ import absolute_import, division, print_function
__metaclass__ = type
from ansible.module_utils.network.common.cfg.base import ConfigBase
from ansible.module_utils.network.common.utils import to_list
from ansible.module_utils.network.junos.facts.facts import Facts
from ansible.module_utils.network.junos.junos import locked_config, load_config, commit_configuration, discard_changes, tostring
from ansible.module_utils.network.common.netconf import build_root_xml_node, build_child_xml_node, build_subtree
class Lldp_interfaces(ConfigBase):