##### SUMMARY
It is a suggestion, the zabbix_template module has a dump option, but I think it needs to be implemented with `_info`.

**reason**

The zabbix_user_group module has been pointed out to go to the `_info` module instead of using dump.
https://github.com/ansible/ansible/pull/58051#pullrequestreview-304208011

The development document also states that modules that return general information need to be `_info`.
https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_checklist.html?highlight=_info%20_facts#contributing-to-ansible-objective-requirements

If need zabbix_template_info module, I created a zabbix_templet_info module, hence I can PR.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
zabbix_template

thanks
author:
    - "sookido (@sookido)"
    - "Logan Vig (@logan2211)"
    - "Dusan Matejka (@D3DeFi)"
requirements:
    - "python >= 2.6"
    - "zabbix-api >= 0.5.4"
options:
    template_name:
        description:
            - Name of Zabbix template.
            - Required when I(template_json) or I(template_xml) are not used.
            - Mutually exclusive with I(template_json) and I(template_xml).
        required: false
    template_json:
        description:
            - JSON dump of templates to import.
            - Multiple templates can be imported this way.
            - Mutually exclusive with I(template_name) and I(template_xml).
        required: false
        type: json
    template_xml:
        description:
            - XML dump of templates to import.
            - Multiple templates can be imported this way.
            - You are advised to pass XML structure matching the structure used by your version of Zabbix server.
            - Custom XML structure can be imported as long as it is valid, but may not yield consistent idempotent
              results on subsequent runs.
            - Mutually exclusive with I(template_name) and I(template_json).
        required: false